All of these suggest to me that the port is not open. Double check your docker creations and verify the host and container ports are really set to the ones you think they are.
Posts by gderf
-
-
Sounds like the destination was some sort of created mountpoint that rsync writes to, but if the device that is being mounted isn't mounted, the mountpoint, usually a directory, will be written to instead. That can cause the drive to fill up.
-
Exactly how and where was the target backup server specified?
-
Actually that is what I wanted to know. Traffic between machines connected to a switch in a LAN isn't seen by your router, so looking there will yield nothing.
What happens if from the omv machine you telnet to its IP address on port 8443 ?
-
How are you testing this? Where (in the network sense) is the machine you are trying to connect from with respect to the machine you are trying to connect to?
-
I imagine once they have a fix it'll be migrated to the official Plex docker.
That wouldn't be necessary as the docker contains or downloads the package directly from Plex.
-
Yes, the system disk can be shared but you have to install the openmediavault-sharerootfs plugin.
I run OMV on a 16GB SSD. It's more than enough.
-
never mind i fixed it
Well is it working now? If so what was your solution?
-
Your UID and GID are both "0", is that correct?
That's a bad idea but not going to prevent it from running.
-
Add following to override.conf in /etc/systemd/system/plexmediaserver.service.d:
[Service]
Environment="TMPDIR=/srv/dev-disk-by-label-data1/plex_media_server_tmpdir"
Unfortunately this can't be done AFAIK when running Plex in a docker unless that variable is supported via an entry in the Environment table of the container. I have no knowledge if the docker supports it or not. If it does it isn't documented.
-
Sorry, I am out of ideas.
Edit:
It may be possible that the Plex configuration library became corrupted. You might try deleting it and allowing Plex to rebuild it from scratch. Also, if you brought up a new container, make sure you either delete the old one or be certain it isn't runing.
-
Sorry, I have no other ideas other than to say if the port is not open it will not work.
-
That doesn't look good with it starting so many times. What restart policy did you set? Don't use Always for now. Use Unless Stopped.
-
They will be there where they were. Deleting a container isn't going remove them. Just don't do a purge if the option for that comes up.
-
Wouldn't hurt. Delete that one and start over. You should read the documentation.
-
Depending on how many media files you have applying ownership and permission fixes can take a while.
Here is what a trouble free startup with an upgrade looks like.
Display MoreCode -
That's not all of it. There either is more or will be more when the update completes and the service starts.
Edit:
And that is the latest version it has downloaded.
-
8GB ought to do it for now. I run on a 16GB SSD, it's now half full, but has been in use for five years.
-
Connection refused means the service is not running. Check the docker log and then restart the container, then look at the log again. If it's crashing the log should offer clues. If the log indicates a normal startup you should be able to connect to it.
-
I don't have any suggestions about your Plex account problems, but until that is solved I don't know to what reduced degree, if any, you can use the Plex Media server.
You might try using the Plex Media Player application on a PC to try and get it logged into your Plex account. I would concentrate on this first. If you can do that I don't see why the server can't be connected.
