This implies a world in which motherboard vendors actually regularly publish updates for their boards, or publish information about a board being officially end-of-life, which, for many consumer boards, just isn’t the case.
Some vendors still have a red flag on their support page discouraging uefi updates unless you’re actively experiencing problems.
I’m in Germany, and it works pretty fine. They’ve got several datacenters around here, never had an issue with speed or latency.
I don’t like that they got that evil megacorp vibe, but what big Internet firm doesn’t?
Well, I need to run two separate tunnels to not run into hairpinning issue, so, some weirdness, I guess. More down to my services, though.
Interesting. As I said, I never tried yunohost. I usually work with podman, and just assign local ports to pods, then route traffic to those ports internally, which seems to work fine.
Anyway, I feel like we won’t be solving OPs issue here. Still, interesting to see some of the problems people with different setups have to deal with.
Yeah, I feel like we’re missing some info here.
I have to admit that I have no experience with yuno. Always seemed interesting, but not like something that fits into my work flow.
If they’re self-hosting at home (which I’m also doing for some services), I’d presume they’re probably running their stuff on a single machine, so I’m not sure where their router would come Into it. The data the cloudflare tunnel process receives should look the same to the router no matter the port it is ultimately sent to, and when it is sent to an address internal to the machine, shouldn’t pass through the router again.
I presume they mean pointing their cloudflare tunnel to direct lemmy.example.com to http://localhost/:[port], and I don’t think there’s any special rules about that port from cloudflares site.
I use tunnels and ports in about that range for all my sites, and don’t have any problems.
Like Fedora Silverblue or OpenSuSE Aeon/Kalpa?