I have wordpress multisite set up on Server 2012/IIS 8 using subdirectories rather than subdomains for each site.
I have set up 6 sites but 4 of them give 404 when I attempt to bring up the dashboard (/wp-admin/) or visit the site
I thought maybe some of the sites had somehow gotten corrupted so I created a new site but it gives a 404 as well.
I cannot see any obvious difference between the sites that work and those that don't.
The only clue I have is that the 404 requests don't even show up in the IIS log.
I have discovered what is going wrong but not why. The sites run on an internal url http:localhost:8100. On the newly created site when I go to edit page it was showing http://localhost/. This is why it was not showing up in the IIS logs.
Unfortunately, If I try to change it, it just reverts. The working sites all show http://localhost:8100/ If I change siteurl and home under settings for the non-working site they also just revert back. So I've discovered the 404 problem but don't yet have a solution
Related
Background:
I have a WordPress website that lives in a Google Cloud-based load balanced environment, and as I work through getting CI/CD setup I elected to isolate one of the servers so that my team could properly run through isolated testing. Since the website is on a regular domain (www.mybusiness.com), I created a duplicate database from our production DB and pointed the isolated server at this new test database. From there, I updated both the 'siteurl' and 'home' values with the isolated server's IP address in my wp_options table, and from there I can access my isolated WordPress site by simply using the URL. However, this is where things get frustrating: the login page simply refreshes after a successful login attempt, while blatantly incorrect login attempts with invalid credentials properly return user login error messages.
After countless hours searching the Internet, Stack, and elsewhere, I've found that the most common solutions are either:
Clear your browser's cookies / cache.
Try logging in with completely different devices (other cell phones, laptops) to confirm it's not a device or local browser-cache issue.
Deactivate and test each plugin,
Confirm your 'siteurl' and 'home' values are correct.
Test your .htaccess file to confirm that's not the problem.
Clear your user's WordPress 'session_tokens' meta_key value.
Revert back to an older / default WordPress theme to confirm if it's a theme problem
Run WordPress's built-in DB repair tool.
Create new WordPress salts and swap them in inside the wp-config.php file.
Enable the 'WP_DEBUG' constant to see if anything in the error logs pops up.
Test non-HTTPS versions of 'siteurl' and 'home'.
After trying all of the above, nothing seems to work: reverting to an older theme (twentynineteen) still presents the same login page refresh issue, and I've gone through every plugin on the server to see if deactivating one or all of them creates a solution - none seem to be the root cause. Error, mysql, and auth logs are also maddeningly clean.
Interestingly, if I add a trailing slash to my IP address-based 'home' and 'siteurl' value, from 'https://11.11.11.11' to 'https://11.11.11.11/' I do successfully get to the correct internal landing page (https://11.11.11.11/landing-page/) - however it just displays a 404 with the basic white screen.
Current WordPress version: 5.4.7
This leaves me with a few questions:
Is this a file permissions issue somewhere? Are there any key WordPress files in which permissions could create this effect?
Would Apache or anything VPC be in play here? I checked out our Apache .conf files, but those don't seem to be the suspect.
Should we look into a WordPress upgrade knowing we're a bit behind with 5.4.7?
Thank you in advance for the help!
My developer recently had some negative argue with me and he has stopped working on my site anymore. I have shifted my site to a new web server and uploaded all the files by myself. (I really have poor idea with .php, WordPress, CodeIgniter).
Now the site is showing error like the below while I click in any link.
Not Found
The requested URL
/news/details/রোহিঙà§à¦—াদের-ফিরিয়ে-নিতে-মিয়ানমারের-পà§à¦°à¦¤à¦¿-রাষà§à¦Ÿà§à¦°à¦ªà¦¤à¦¿à¦°-আহà§à¦¬à¦¾à¦¨
was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to
use an ErrorDocument to handle the request.
how can I make the site live now?
my sites url: http://www.dhakagazette.net
the index now can be located at http://www.dhakagazette.net/.index.php
please suggest to make my site live.
Thank you
I am hosting a site locally via MAMP, but somehow while editing sidebar (tried to edit widgets), site went blank and it cannot give me access to wordpress admin panel. It shows up 500 error and blank page.
Site has multiple themes assigned to different pages, so when I try to access homepage (arcade basic theme) it works fine. But when I try to access Shop (mystile theme), it shows blank page and 500 error.
The 500 error is also received when I try to access admin panel via wordpress dashboard (on my homepage).
what can I do?
Just in case you didn't know, 500 errors mean there's a server misconfiguration somewhere.
This could easily be down to an error in coding, which clearly this sounds like.
You would be helped greatly by looking in your apache error logs (usually in your log folders), this should tell you what caused the error - or you could also try turning PHP error display on, which may display the same information but on the screen.
Once you find out where abouts in the code the error is being generated, update your answer, along with an excerpt of that area of the code, and others may be able to help you better.
Another suggestion would be to try using an IDE software application to write your code, as this will flag up any errors as you type them. Personally, I use NetBeans.
I'm having some trouble with a drupal page. The website is loading and nothing is out of the ordinarty. But when you load the page with Google Chrome development shizzle (when you press F12) and put it on Network and then reload the page, you see that the first thing that happens is receive an 404 error.
It's not that big of a deal but our monitoring system says the website is offline because of this.
Does anyone knows what is going on? I have absolutely no idea why this is happening.
I'm running into this exact problem with a D7 site on a new server that has PHP 5.5.9 installed - the page loads but the HTTP header says "HTTP/1.1 404 Not Found" for all pages but the homepage. If I work out a solution I'll post it here.
Update: It turned out my problem was that mod_rewrite was not enabled, once I enabled it the site started working correctly.
Drupal allows customizing 404-403 error pages. Probably, your site (by some reason) displays content on 403/404 pages.
At first, clear cache (using web ui or drush).
This can be 1-page issue (check /user/login, admin pages, node pages). Maybe, only your front page is not found.
If this is not 1-page issue, check and disable customerror module (if you has one installed).
I have one site in drupal and abruptly site hit is giving error as "This webpage has a redirect loop".
The webpage at http://example.com/install.php has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
Here are some suggestions:
Reload this webpage later.
Learn more about this problem.
Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many
redirects.
can any one tell where I am going wrong?
Try to upload a static HTML file to the same directory and try to access this file via HTTP. If it gives you the same error, then it's the directory permission.
The common cause is that you don't have the permission to browse the folder. You can fix it by giving execute permission for everyone.
I had the same error message. I found this issue on drupal.org from which I got the idea to look for install.php that had been deleted by Softaculous (automated installation software).
Copying install.php from a freshly downloaded package solved the problem.
I just recently had this issue today working on a dev site. Only the front page was resulting in a "Too Many Redirects" error, all other pages for the site worked correctly. Turned out to be an issue related to the hosting, turned off caching and everything worked out fine.