I have ISPConfig 3 installed on my server, and have 4 sites running on it. One site has been having issues, so I purged everything and rebuild it all from scratch. The issue is when I go to edit.php?post_type=page I get a 403 error from ISPConfig. No other pages within edit.php or on any other sites, just this one (this error is what caused me to rebuild the site). Thoughts on how I can fix this? I have tried deleting, and recreating the .htaccess file, I have tried file permissions on all files, and literally rebuilding the site in ISPConfig and uploading a fresh database and set of files.
You receive a 403 error from your web server (nginx or Apache), not from ISPCOnfig. ISPConfig is a hosting Control Panel, its not the web server. Check the error.log of the website, and then you know why the web server throws that error. The only thing that you must ensure is that the files are owned by the web user and client group of that site. If you upload it via FTP or use an SSH user on this site, then permissions are set correctly automatically. If you use the root user, you must set the correct owner of the files.
So I look at the sites error.log with a tail -f error.log and nothing loads when I go into the page that is throwing the 403. When I do a tail -f on the error.log in /var/log/apache2 nothing loads on the error page. When I do a tail -f on /var/log/ispconfig/httpd/site.com nothing loads as the page throws a 403. Any other places I should be looking?
Check access.log as well. A 403 error means "Forbidden", which isn't necessarily something that is logged in error.log Why the website is throwing this error can have several causes. It might be because of something in the webserver config. It can be because of a directive you have set in ispconfig. If the website has a .htaccess file something in there can be a cause. I can go on for a while. Finding the error in the logs is your starting point to solve it.
This is the issue. NOTHING comes up in access.log on the site, or error.log. The settings in ISPConfig are exactly the same as the other sites that are working. I am at my whit's end here trying to find this error... any help in locating the issue would be greatly appreciated.
I'm with @till on this one. Or you haven't (correctly) set-up SSL for the website in question, leading your browser (which most likely is using https and not http) to the first SSL accepting website (alphabetical order) in your webserver. So you might be looking in de wrong logs. There is no way not at the very least your request isn't logged anywhere.
