lease fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
**Parse error** : syntax error, unexpected 'finally' (T_STRING), expecting catch (T_CATCH) in **/home/tcmullet/public_html/certsage.php** on line **599**
(The asterisks don't show on the screen.)
My web server is (include version): Apache(?) ver. 2.4.62
The operating system my web server runs on is (include version): Linux (Version is whatever Godaddy supplies. They don't tell me the version.)
My hosting provider, if applicable, is: Godaddy
I can login to a root shell on my machine (yes or no, or I don't know):
I don't know.
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
cPanel ver. 118.0 (build 13)
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
What do you mean by "my client"??
I've been running certsage.php since Mar 2023 every 3 months (sooner than the 3 month expiration usually). This is the first time it's gotten an error like this instead of the main screen of the certsage program. My current certificate expires on 2/19/2025. I greatly hope to be able to renew it by then.
From what I can tell via cpanel, PHP version 8.1.29. certsage is still 1.4.0
FWIW, I have to pay $3 a month more for now so that godaddy provides "PHP Extended Support Level 1". I think this relates to keeping PHP compatible with PHP 5. I have to do this b/c when I let them switch me to "the current", my site could not load/execute php files. So they switched me back and resumed charging me $3/mo extra for hosting.
The error suggests a php version too old, and that "Extended Support" might have broken something -- finally was introduced in php 5.5 and Certsage requires 7+
It seems that Godaddy had moved me from 7.x back to 5.4 when I elected NOT to migrate to something higher like 8. Certsage always worked as I (apparently) was always on 7.x. When I didn't want to go to 8, they stuck me back at 5.4 causing today's certsage to bomb. (I've never bothered to become conscious of PHP versions.) 7.x works, but still charges the extra $2.99. I found bug in my code that caused 8.0 php to bomb. I now know how to easily change PHP versions. AND my certsage.php 1.4.0 has worked fine again! And I now have syntax errors to fix in 100+ php files, something I can easily handle at leisure. Griffin, do you think I should change to certsage 2.0? Will the sequence of events I go through to use it change or stay the same as with 1.4.0? (But I'm very happy I beat the deadline for SSL expiration, as well as learning about PHP migration issues.)
lease fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.