I recently migrated my website to DigitalOcean under plesk panel using all in one migration plugin. I kept having issues with 404 error only for pages that used permalinks configured as %postname%. For better URL format for my Content. But now if I enable the permalink I keep getting 404 error.
I used the popular suggestion of editing the nginx conf file through (through putty).
https://www.cyberciti.biz/faq/how-to-configure-nginx-for-wordpress-permalinks/
I wasn't sure of the save and exit step given after using the editor. ctrl+X shows a set of ^O^D commands. I pressed ^O and restarted it.
Now my entire website looks broken. Due to many 500 internal errors. What am I doing wrong here? kindly help me out please?
My website address is https://ourmoon.life/
Related
i have installed WordPress on my Ubuntu machine. i have also installed all the required resources like PHP, MariaDB and others.
At first i navigated to the sample site and i even made some few changes. Then after tempering with settings, when i try to go back to my sample site am getting an error.
This is the image error.
I have tried to do everything i could but still getting the same error.
How can i resolve this
I installed a customer project on my local machine.
I want to create a new REST API route.
On the live website, i can see the wp-json data.
But when i call the wp-json on localhost, i get this message:
I have a couple of wordpress websites on localhost and everyone work without any problems. Instead of this wordpress installation. I already uninstalled all plugins and the message still appear.
Has anyone an idea to solve this problem?
This could be a permalink issue, go to Settings > Permalinks and change the setting to "Post name" and save settings, then check if you get the same issue or not.
I've been researching this error and can find similar issues but no solutions. I am running WordPress using XAMPP on my local server.
I imported a WordPress page and all was well. The problem is I added a bunch of new services, and when I try to access them I get a 404.
If I create a new post or page, they work fine. I reset the permalinks, no luck. The errors are only with the services. I'm really stuck on this, any help would be appreciated!
I'm currently running into a strange problem with Wordpress on my production server. When I try to visit non-existing URLs, Wordpress doesn't trigger a 404 when the url has more than 3 segments, for example:
These pages don't exists and trigger a 404 page:
http://example.com/9
http://example.com/9/9
These also dont exist, but don't trigger a 404 page and show the homepage (with 200 response code):
http://example.com/9/9/9
http://example.com/9/9/9/9
http://example.com/9/9/9/9/9
On my local machine all above pages show a 404 (as expected). The server (and my local machine) are both running nginx >10.16, both nginx vhost configs are almost equal. Running PHP72-fpm.
Debugging I already did:
Disable functions.php in theme folder
Disable all plugins
Switch to other theme
Disable cloudflare caching
Flush permalinks
All without any success unfortunately.. I'm kinda running out of options for debugging, I hope anyone has got any suggestions!
I just found out that locally I'm running PHP73, on the production server PHP72. I've just upgraded the production server from PHP72 to PHP73 and the problem seems to be fixed!
I've seen some other people with the same issue on net,
but the solution that worked for them (updating the .htacess file), didn't go very well for me!
I used buddypress to migrate my wordpress site to my local pc, but after everything is setup, only the home page is working, other posts or pages are getting 404 errors, I also tried to deactivate plugins and changing the theme, but nothing worked.
I'm on windows 10 and i'm using wampserver 2.5.
I think that the issue is caused by Apache, but I don't know how to fix it!
my Apache version is 2.4.9
Thanks in advance guys :)
Your site’s permalink (WordPress Admin > Settings > Permalink) is set as Default, please change it to any of the other option available below. e.g: Day and name, Post name etc.
Then you’ll be able to access the board instead of the 404 error.
Another way is troubleshooting:
WordPress sites can complicate the 404 troubleshooting process. Why? WordPress is a content management system that processes its own internal rewrite array as a part of its permalinks feature.
The first step to troubleshooting 404s is to figure out whether the 404 is being caused by the web server or by WordPress.
Static file
If your file is static (e.g. a jpg image) open your FTP client and verify that the file exists.
As an example, let’s say that the URL http://example.com/wp-content/uploads/picture.jpg is producing a 404 error. You will want to:
Open FTP Client and connect to your server (if you don’t know how to do so, read this.)
Navigate to the file’s location
Verify that the file exists
If it is does not exist, you have found the source of your 404.
However, it it does exist, yet pulling the URL up in a browser results in a 404 error, continue on to find out whether the issue is web server-based or WordPress-based.
Reference Link: http://websynthesis.com/fixing-wordpress-404-errors/