Lol how funny. I was also very into modding the PSP growing up. I had a couple of Pandora batteries. The only reason I caught onto it was because my name is also Alex haha hello fellow Alex!
tux7350
..... are you the DaX from the PSP modding scene?!
Oh boy I went down this same rabbit hole awhile ago. Here is a git repository that will explain why this happens and also offers a fix on how to modify your IP tables to ensure that docker respects the UFW.
It's really not that hard to use a local account. When it askes for a Microsoft account just hit SHIFT+F10 then type in the command "oobe\bypassnro" and the pc will reboot. Now just don't let the computer connect to internet, and when it askes for internet hit "I don't have an internet connection" and then it will let you continue with a local account.
....I admit though... as I typed that out its pretty annoying lol Not hard, but like... just annoying.
It shouldn't mess with your current routing but if you're running other VPNs you may run into issues.
After you join the machines to the tailnet, each machine gets a new IP address ( only visible to other machines in the tailnet), by default it's a 100.x.y.z you can check the tailnet for the device IP.
Now you can keep the port closed on your router and it will still be accessible over the usual lan ip and port. But when you want to access remotely, turn on tailscale and connect using the tailnet IP.
Another cool thing you can do with this setup is turn your home server into an exit node. By default it will only route things that are in the tailnet (100.x.y.z subnet). But if you turn your home server into an exit node you can funnel all your traffic back through the exit node. Instant free VPN back home!
Unencrypted HTTP can mean that anyone can see your traffic as it passes through their network. Your ISP will see that traffic. If you're streaming pirated music and you're in a country that cares about those things, might not go very well. From a security stand point though, you still wouldn't want to trust the authentication on the open port. A vulnerability may exist that you don't know about. It's always better to keep them closed and add another layer or two between your home computer and the public.
Tailscale let's you tunnel into your home network without opening any ports, and it encrypts the traffic. Much safer way of doing it.
Another tip, please be very careful when exposing ports to the public. With docker you're already mitigating your attack surfaces but an open port allows anyone to make a connection and there are lots of bots out there looking for open ports and vulnerabilities. A good alternative would be to setup wireguard and instead then connect through that or if you like simplicity check out Tailscale.
This is kinda how I've come to look at it. You cannot ask questions of fact to a machine that works in probabilities.
Ha, ya know? I think I know some people who will just regurgitate whatever input they receive
........
:(
Mullvad let's you write down an account number on a piece of paper and mail it in with cash and they'll activate it.
I've got a galaxy fold 4 that I pre-ordered, so over 2 years old. I've rocked it this whole time with no case and dropped it plenty of times. It's got a couple of scratches on the hinge but has been the most solid phone I've ever owned. From my experience, your claims are simply not true.