this post was submitted on 05 Sep 2026
6 points (100.0% liked)
technology
24455 readers
84 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
your container group and user id can run into networking issues if you responsibly denied the access to everyone (guest) except for current user (this is in environment variables, if I recall correctly, you can go to admin numbers of gid/pid, check if it fixes stuff, and then deescalate them to something working, i think container can’t claim privileges higher than docker itself, so there is some shit to troubleshoot there)
check that your firewall on the server is not blocking (or clashing, check with netstat) port range you use and/or docker itself (i once run into firewall rule blocking python in the thingy i was using, that wasn’t fun), rebind the port to different one in any scenario, reboot, check again.
check router firewall rules for local networking, check you are using correct ip of server (check you can ping server as an entity, bind it to static in router, and remove old leases, reset router if you can’t remove old leases).
this is general order i fumble containers when i forgor
(also, you can enter into terminal from inside the container, and check out what it sees networking wise)
I'm really sorry but I actually don't know what half of these words mean.
This is why I feel like this container stuff is a really weird thing to make normie desktop users do. I'm out here like Hank Hill, "do I look like I know what a jpeg is?"
Plex was an easy MSI installer on Windows, I'm just so lost.
okay, first search “group/user id in docker settings” (it’s a variable that assigns as which type of user container masquerades as (admin/user/guest), if your system is restrictive enough, default numbers might lead it to run as guest without any rights to network access, those numbers are a string in environmental variables inside a docker and sometimes are missing from compose files, you’ll have to reintroduce them manually
second, your default assigned port in deployer or whatever might run into system restrictions of the host (another service running on that port or port range being blocked by firewall for some arcane reason), search for docker port problems or something, it’s usually what people will discuss. (although, if you see webui, that part is likely fine), *but checking with netstat (ipconfig? if you are on windows) still might show you something about the port (if it’s missing, that points to first problem being likely)
lastly, router maybe doing shenanigans on your server, specifically (you can try it out as entering not 127.0.0.1: port number, but as local server ip (192.something by default): port number on your server, which in theory will route request inside network once, although that maybe swapped silently, so not conclusive). can you ping your server (not plex, just server) from another device?
(Also, set it to bridge for a try)