InEnduringGrowStrong

and let’s hope that the login page doesn’t have any vulnerabilities…

Home assistant also supports mTLS.
home assistant is something you’d likely ever want to allow from a handful of trusted devices, so deploying a client certificate on them can make sense.
This way a non-onboarded device doesn’t even get to the html part, it’s denied upstream by a reverse proxy before HA is involved.

I’m a big fan of mutual TLS, which I just do in nginx reverse proxy.
Client certs get installed on trusted devices and then it’s mostly seamless.
Not every app will support it, but I use Firefox as a fallback for stuff that doesn’t, or my VPN.
TBH, I’m just happy homeassistant supports it as that’s the one thing I’d rather be as seamless as possible.
Other things I don’t mind having to connect a VPN for, like jellyfin, which I don’t currently share with others.
For nextcloud I’m currently not running mTLS as it wasn’t supported back then and I had to share some links with some people where I wouldn’t deal with certs. I think mTLS support has been merged since, so if you just use it for devices under your control, or might be viable

Not necessarily since the initial layers don’t have the space to be squished properly, subsequent layers can show the same problem, except they’re too close to the previous layer instead of the bed itself.

That said, the picture didn’t load before but now it does.
Qith the picture, this looks kinda like wet filament to me where it’ll kinda bubble here and there.
I’ve also spent way too much time hunting down underextrusion what was ultimately just the filament that had a weird undersized diameter like 1.6mm.
Diameter that’s off but consistent through the roll can be compensated for in the slicer, inconsistent diameter not so much.

All good answers so far.
Basically your internet gateway doesn’t support what’s called NAT hairpin, also called NAT loopback.

The DNS solution is better anyway, and that particular setup is called split-horizon DNS, which basically just means your internal DNS requests get different results than ones from outside your network.

Nozzle might also just be too close to the bed.
Mine did a kind of of “tock” sound when it struggled to extrude.

An out-of-band means of communication is indeed very useful to have.
We have a matrix channel, which is linked in the instance sidebar after the rules.

Here: matrix.to/#/#sh.itjust.works:matrix.org

Thanks for the ping