Continued smol brain adventures in Docker
So I managed to get Docker set up (I think) with the help of a script called Deployrr, then used the linuxserver.io docker file thing.
The plex media server runs and I can see all my content in the web UI, however none of the plex apps can connect to it.
Can anyone help point me in the right direction to fix this without doxxing myself?
Firewall. If you can connect to it locally but not externally it is the first thing I would check.
ⓘ This user is suspected of being a cat. Please report any suspicious behavior.
Okay, so if I disable the firewall or set Default Incoming Policy to allow, it works great.
I’m pretty sure that’s a bad idea, though…
That is a bad idea. Can you set specific ports to be allowed? If so it should be port 32400 per the Plex docs.
ⓘ This user is suspected of being a cat. Please report any suspicious behavior.
Nice! I got that tcp port added and it connects
5 seconds later…
EasyAudioEncoder fails with exit code 13, but trying to chmod EAE doesn’t work
Doesn’t docker bypass firewalls like UFW by modifying iptables directly?
I know they use iptables to do their stuff, but does it make them open like that? Sounds like a terrible idea to me. Docker can’t know if I want that port to be open to the entire world or just locally.
ⓘ This user is suspected of being a cat. Please report any suspicious behavior.
It does that when you expose container ports unless you explicitly bind them to localhost and yes it’s a terrible idea.
Oh yeah I was similarly shocked when I first learned that even if you block a port in your firewall docker says no you’re open. If you’re just doing it on your home network and not port forwarding it in your router and exposing to to WAN I guess it’s not so bad
It might be specific to UFW?
Edit: No the docker docs state also firewalld. And presumably if you’re making the firewall rules yourself, depending on how you can also fall into the same trap.
Edit 2: and bazzite potentially uses firewalld
ⓘ This user is suspected of being a cat. Please report any suspicious behavior.
I’m sorry, but why over complicate things with Docker when it can just install natively on the OS? Sure, isolation… But holy hell, to me, it seems like you’re over complicating this piece. Save Docker (or Podman) for apps that suck and only have that as an option…
Scho docker by default runs on a separate network and resulting IP entirely unless you bind it to the host network by port or use a reverse proxy that can expose. The Plex docker also has a host network setup which I imagine handles this for you which you should try because it will act more like a normal local service. If you have a firewall that is catch all then it will block the docker IP which is something I bashed my head against for a while. If you wanna debug where your service is running there is netstat command eeeer. -tulpn I fink need to go get my laptop. Then you can list all the IPs and ports bound and find where Plex is running and work from there
sudo ss -tulpn
Or
sudo lsof -i -P -n
This sounds like it’s a networking issue. Are you able to access the webui from other computers besides the computer that Plex is running on?
The linuxserver docs have a snippet on configuring networking for plex.
Are you able to access the webui from other computers besides the computer that Plex is running on?
Nope :(
I’m trying to use the host network mode which is recommended.
Why not just install Plex without docker? There’s a package for it on the AUR and it would simplify a lot of things where the only thing you’d have to worry about is opening the ports on your firewall (which you can do with a program called ufw quite easily).
Docker is mostly meant for cloud/constrained environments but since you have a Arch based distribution on a personal computer, docker is very optional.
Ah-!
I forgot I could just do that aaaaaauggh
You’re still trying to run this on bazzite aren’t you?
Just get a minipc from ewaste, install debian, and then install the Plex package without docker.
You’ll have a much easier time
Can you post your docker config? That’d be the most useful thing for people to help troubleshoot
And quick sanity check. Is the docker container running on a computer in your home or did you install it on a server somewhere else?
It’s in my home, yes!
Ah I missed that you used Deployrr to set it up.
Professional Networking: Advanced Traefik reverse proxy configuration Flexible exposure modes (Internal, External, or Hybrid) Multi-server and multi-domain support.
This is almost certainly where you’re running into issues if you’re not familiar with things like reverse proxies. Imo Deployrr looks like it way overcomplicates things if you’re just looking to run a simple Plex server set up
I took a peek into your last post and saw someone recommended Deployrr to you. And maybe that’s the way to go if you’re trying to set up the full *arr suite like you mentioned. But it seems like you’re trying to learn a whole lot at once. Not that you can’t figure it out but personally I’d start small and add complexity over time as you get more familiar and figure out what you actually need/want in a set up
They don’t have a simple text guide in their repo? I’m not sitting there watching their 2hr setup walkthrough video for some <1k star repo that’s trying to charge people $30 for support. Not directed at you OP, just ranting about their project
Yeah. I definitely want radarr and sonarr and Bazarr, which seem to maybe require doing this in docker, but that stupid ass $30 script fucked me because I don’t want to pay for it?
Ugh! How do I undo that?
Docker compose and binding relevant ports to host feels like the simplest setup but a cursory glance at their repo it’s like they want you to be deploying this to k8s or sum shit. Today I will set up a highly scalable netflix for 1 user. Something else I self hosted insisted on me using traefik in it’s documentation like my guy I’m running this on my Lan I care not
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)
When you go to the local web UI, there should be settings somewhere the include some information on the network status of the instance.
I’m not near my Plex server and made my laptop unbootable so I can’t give you more detailed/up to date info right now.
