It seems like the asteroidsathome(.)net domain is down, and only the www.asteroidsathome(.)net works, making the login break (since the login page redirects the user to the non-www domain).

So far, I found a workaround by editing my hosts file (so that the non-www domain is linked to the www domain's ip), but that's kinda annoying and might not work for mobile users.

I'm not sure what all has changed since the above post, because the IP for both asteroidsathome.net and www.asteroidsathome.net is the same, according to my computer.

In any case I've found adding www. does work around a problem I've found lately. My usual DNS resolver is blocking asteroidsathome.net, but with the www prefix it does (eventually, slowly) load. It's still too slow for reasonable use, so I'm bypassing my usual DNS resolver's malware blocking mode at the moment. What's really concerning is the resolver does seem to think it's actual malware on this site (I'm using CIRA Canadian Shield, the "protected" one, DoH configured in my browser). When I turn it off in my browser, my router still uses the same resolver, but DoT instead of DoH, and it can fallback to Quad9 (I use 9.9.9.11) which also is supposed to block malware.

I believe CIRA is actively blocking because, when I attempt non-https access to asteroidsathome.net in a browser with DoH turned on, it redirects to a CIRA blocking page. Oddly enough, when I use wget to manually check what's going on, it shows non-https does a normal redirect to https://asteroidsathome.net, not to CIRA (and it then connects and downloads the page fine).

The full solution to this I believe, is simply lobbying CIRA to reexamine why they are blocking asteroidsathome.net. I will send them a message, but I imagine it would help if the website operators do so as well.