Search results

I'm having problems adjusting the cache at mercury.photo. I've got the following rules at the server and VM level in the OpenLiteSpeed dashboard: application/x-font-ttf=A2592000, application/javascript=A2592000, application/json=A2592000, application/pdf=A2592000...

I was able to track down the offending certificate to /usr/local/lsws/conf/example.crt Edited the httpd_config files by commenting out the references to this cert & its corresponding key and replacing them with the paths to my LE certs and then reloaded the server. That eliminated the bad cert...

OK, it wasn't .htaccess; it was the main WordPress settings. But I'm still getting a certificate error because of the self-signed cert. I didn't create this cert so I don't know where it came from or where it's located on the server. Any idea how to revoke it?

I was about to do that. Will let you know!

I moved a client site to a Google Compute Engine + OpenLiteSpeed instance. Just now updated the DNS & went through the interactive setup via the CLI. Set up the virtualhost listeners & issued the LE certs. When I visit the site URL, the browser redirects to the server IP and I get a certificate...