...
A SSL error is one of the more likely issues, you should see a notice about the site no longer being trusted. Staging uses Let's Encrypt certificates while Production uses a GoDaddy certificate that IT manages.
In production
- If an SSL error occurs, in the browser check to make sure the SSL cert is valid for the current date.
- Go onto server and check the SSL file's name and location match the name and location in the apache config file at
/etc/apache2/sites-enabled/sufia-project_ssl.conf
- If the file date covers past today and the name and location match, check the permissions on the file with
ls -l
to make sure it can be accessed. - Check the current SSL file on XXX and md5sum it and compare it to the md5sum of the file currently on the server.
- Check via the command line with XXX to see the expiration date of the
On staging
- Check the expiration date on the SSL certificate
- If expired check the crontab for certbot
- Try running certbot manually
- Check the apache config file
/etc/apache2/sites-enabled/sufia-project_ssl.conf
to make sure that the name of the file points to a soft link that has the most up to date version of the certificate file.
Info |
---|
Related articles
Filter by label (Content by label) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...