With the 3.3.1 version?
Yes - sorry!
I suggest trying again. I've had 9 consecutive successful tests on my end.
I have other domains on the same host (e.g. CertSage) that have an EC certificate successfully installed.
I'll have to look into this more later for download issue. Seems like hosting provider changed something regarding EC keys.
I'm seeing that too. Odd. Seems like maybe some kind of caching is happening. That's not something CertSage does.
Do you have some kind of caching enabled? Did you modify certsage.php in some way?
I'm not even seeing a password error no matter what I submit.
Maybe related to LiteSpeed?
curl -i shawcottage.farm
HTTP/1.1 301 Moved Permanently
date: Mon, 25 May 2026 20:18:29 GMT
server: LiteSpeed
Because that is not the same as:
No caching enabled unless it's a Namecheap default that I'm not aware of and no, certsage.php not modified other than changing the data directory. I'll start with a clean certsage download tomorrow.
I think there's something strange about the way that domain name is having its pages served.
I have done a clean download and install of certsage.php, tried different browsers, Ubuntu and MacOS and sill have the same problem, but only with this domain. The site itself, (php, javascript, MariaDB) works perfectly and other sites on the same hosting platform work perfectly with CertSage. I can't see anything different about this site.
CertSage is not the issue, so no amount of downloading it or different browsers will matter. The problem is with what is serving certsage.php. This is obvious from the fact that I'm able to load the error page from your run of CertSage, which isn't even possible under normal operating circumstances of a webserver. I think you may have an orphaned/broken webserver process (LiteSpeed).
Try changing the version number inside certsage.php to 'test' and you'll see what I mean. When you try to load certsage.php from a web browser, the version number likely won't show 'test', which would mean that your webserver isn't actually serving from the certsage.php file.
Apparently our host, Namecheap, have temporarily disabled LiteSpeed Cache Manager, due to security concerns. Could this be causing the problem?
Maybe. Not sure.
Oh... hmm...
I think I may know what's happening. I think I may have made a bad assumption of the origin of the error.
I think it's ARI related. More later.
Please attach the responses.txt file from the CertSage data folder for shawcottage.farm referenced on line 19 of the certsage.php file being served for shawcottage.farm.