website down. http 500
-
- Posts: 22
- Joined: Thu Aug 25, 2016 11:58 pm
website down. http 500
I can't access a domain on my vestacp install. I get a http 500 error. All the services are running. Rebooted server. Still won't load. Site is pingable and vesta interface is accessible. It has a letsencrypt certificate for https, set up with the vesta cli.
-
- Posts: 22
- Joined: Thu Aug 25, 2016 11:58 pm
Re: website down. http 500
I've narrowed it down to a problem with the https. If I disable the .htaccess https rewrite and go to the http site, it works fine. The https site doesn't work.
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: website down. http 500
what do you have in your .htaccess, please paste here
-
- Posts: 22
- Joined: Thu Aug 25, 2016 11:58 pm
Re: website down. http 500
Code: Select all
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: website down. http 500
Did you migrate your WP site recently from another server?
or
Enabled HTTPs recently ?
If so, you need to delete permalinks and let WP create them again :
1. Delete your .htaccess
2. In your WP-Admin ->> Settings ->> Permalinks and set it to DEFAULT ->> Apply
Check and if the URL's work now, set the URLs back to PostName
or
Enabled HTTPs recently ?
If so, you need to delete permalinks and let WP create them again :
1. Delete your .htaccess
2. In your WP-Admin ->> Settings ->> Permalinks and set it to DEFAULT ->> Apply
Check and if the URL's work now, set the URLs back to PostName
-
- Posts: 22
- Joined: Thu Aug 25, 2016 11:58 pm
Re: website down. http 500
No. The site was working fine. Only thing that happened was the cron job to update the lets encrypt certificate ran. It had a chmod 755 error.
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: website down. http 500
PM me your domain... I'll check