xyzulu

Ahh ok.. probably best to post in here then: https://whmcs.community/community/21-feedback/ .. or via a public form: https://www.whmcs.com/contact/

Check your webserver logs as a first step..

The directions to: are not correct im my opinion. Instead, you should use something like: @WHMCS John ?? Apart from that, the cli upgrade process is so much better than any other WHMCS upgrade I've done before.

Share the result to help others who come across this thread in the future 😉

Answering myself.. a google search of the whmcs properties led me to this: https://help.whmcs.com/m/updating/l/1465032-updating-whmcs-on-the-command-line

I'm only able to find documentation on installing via cli, yet a reference is made to upgrading as well, see: https://docs.whmcs.com/Install_On_The_Command_Line How do we update via cli?

Test another server? ie gmail.com to see if the issue is also happening there?

What email provider? I have no issues with pop importing (for years).. usually gmail or google workspace accounts. There is also a new oauth gmail/google option worth trying.

This is a TPP issue. They should release an update to their WHMCS module to handle .au domain eligibility.

Do you use a 3rd party module/plugin.. ie a domain registrar or hosting provider who's API could have been having issues thus causing pages of yours not to load?

You will need to connect to your cPanel server via the ssl port... port 2087. The error above indicates you are trying to use http only.. port 2086

Do a test upgrade on a staging site first, see: https://help.whmcs.com/m/updating

Turning up error reporting may help, see: https://docs.whmcs.com/Error_Management#Error_Reporting_and_Display

It might be a server resource issue? If there was an "issue" with WHMCS and CSF you would be seeing blocked pages etc and entries in the CSF log regarding them. Sorry.. probably not what you wanted to hear.

Exactly.. I just want the right people/person to see this bug as I have no confidence it will be fixed (albeit minor). A good developer would have fixed all logs the first time around, not just for one entry (email log entries).