NAT to extremes… it’s Starlink so I think I’m almost completely obfuscated from the internet entirely.

quite frankly i don’t really host anything that needs to be accessible from the general Internet so I never bothered with workarounds.

100% is lan only cause my isp is a cunt

i got the random Dell SFF optiplex with 16gb of upgraded ram and a i5-4690 sitting at the girlfriend’s house because she’s the only one with an ISP that still allows public ip’s.
It runs Minecraft.

at home i have my old 9yo retired gaming desktop doing seedbox work and mostly just running BOINC to donate compute power to science… and also keep my feet warm lol

yeah. that’s it. i really don’t do shit even though i totally could.

me after 15 years of intermittent learning self hosting:

i have the one random office PC that runs minecraft

…yeah that’s it

A lot of people, myself included, got pissed off at the Pi Foundation during the chip shortage for exclusively shipping boards to business customers who vacuumed up every single one of them faster than any consumer could. You couldn’t shake a stick at any Pi for less than 3x MSRP from scalpers, which at that point, you’re literally better off grabbing a NUC. They showed their true colors and it left a bad taste in all our mouths, and I will never be buying another Pi.

Really the ARM hate just comes down to ecosystem support. A lot of the SBC’s from other Chinese suppliers have mid kernel/OS level support at best, and a limited range of compiled software. For a lot of purposes, going x86 simplifies setup and opens up the software realm so, so much.

Generally speaking, any device (“server”) hosting a “service” NEEDS to be assigned a static IP. It simplifies routing significantly and avoids random break problems because DHCP is incredibly stupid at times…

Is there any specific reason you need DHCP to assign an IP to your main hosting server vs setting it all statically?

Moving it to it’s own system will not fix the routing problem. You can probably still leave it on the USG.

You should be able to set a fixed static IP on your server, and then also statically assign that same IP to your server in your USG DHCP config- as long as they both are “thinking about” the same IP I think routing should work correctly.

If that breaks, try just assigning the static IP only from the USG side or only from the server’s side. I’m 90% sure that even if the USG does not have your server machine in it’s client list, if it sends broadcast packets to an entered IP looking for the unifi server, and the unifi server is listening on that manually set IP, they should be able to talk.

disclaimer: i am high as shit right now and this may be bullshit