I can confirm the problem. And as Hoikas already suspected in the other topic, it *is* related to the move to HTTPS. The cheap HTTP client I am using in Alcugs (essentially a hand-rolled one on directly on TCP sockets) does not support HTTPS. Hoikas, you caught me off-guard here
(The reason it still worked for you is the authentication cache, I suspect.)
Now, is there any chance that we could have, at least temporarily, a subdomain that provides the `cgas.php` *without* enforcing encryption? The script (as far as I recall) already validates the sender IP address, so it can't be used by anything but the Shard. Furthermore, it forwards the challenge-response protocol that's run between client and Shard, and doesn't transmit the password in unencrypted form. So it's not super-ciritical to do that via HTTPS (unlike, say, the board login. Thanks for going encrypted here!).
In the long run, of course the server should support HTTPS. But I have no idea when I'll get around to implement that, I never worked with curl or wget (which would be the obvious candidates to use here). Of course, the code is all open source, so anybody could help here