I noticed today that test.muklet.com was throwing me a “something went wrong” every time I tried to access it.
I’m getting a consistent 404 for both test.mucklet.com and api.test.mucklet.com. I sure hope it hasn’t been removed, it’s very useful for developing under much more controlled, and less chaotic conditions.
1 Like
Oh!
Sorry. My mistake. 
No, not removed, but made temporarily unavailable to try to pinpoint that websocket bug in Apple’s iCloud Private Relay.
I will restore it later today.
1 Like
Okay. Skip the “later today”. I just restored it back. 
The “missing” part was that I had disabled TLS, so it was still accessible at http://test.mucklet.com
But I have reactivate the encryption again, and http once against redirects to https
1 Like
I thought I had noticed something funky with http still working. I’ve got HTTPS everywhere in my browser so it kept shoving me into the https version, so I never properly saw it work there
1 Like