sudo tar cfz /tmp/Logs.tar.gz "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs"
Drag & drop that Logs.tar.gz in the reply window,
Let it upload,
wait for the URL link to show.
then hit Reply
Sorry I did not know how to send the file after it was generated. follows the attached logs.
Logs.tar.gz (161.6 KB)
From your logs, the server is detecting its primary address to be 192.168.1.2 based on the VM config.
May 11, 2019 21:34:20.499 [0x7f5bb7a09780] DEBUG - Detected primary interface: 192.168.1.2
May 11, 2019 21:34:20.499 [0x7f5bb7a09780] DEBUG - Network interfaces:
May 11, 2019 21:34:20.499 [0x7f5bb7a09780] DEBUG - * 1 lo (127.0.0.1) (loopback: 1)
May 11, 2019 21:34:20.499 [0x7f5bb7a09780] DEBUG - * 8 vnet-external (192.168.1.2) (loopback: 0)
May 11, 2019 21:34:20.499 [0x7f5bb7a09780] DEBUG - * 9 vnet-internal (10.0.69.1) (loopback: 0)
May 11, 2019 21:34:20.499 [0x7f5bb7a09780] DEBUG - * 12 vnet-dmz (172.16.10.1) (loopback: 0)
May 11, 2019 21:34:20.499 [0x7f5bb7a09780] DEBUG - * 14 virbr0 (192.168.122.1) (loopback: 0)
May 11, 2019 21:34:20.499 [0x7f5bb7a09780] DEBUG - Creating NetworkServices singleton.
May 11, 2019 21:34:20.500 [0x7f5bb7a09780] DEBUG - NetworkServices: Initializing...
This server has 3 networks, 192.168.1.2 is for the internet. 10.0.69.1 is for the LAN and 172.16.10.1 is for the DMZ. Before reinstalling the server it was already like that, with the same addresses.
I would recommend performing the SSH-tunnel technique to get into it.
Once in it, I would set the preferred adapter to the one you want for the LAN (?)
I tried the ssh tunel for mac and windows, neither of them succeeded. The important thing is that it works, which interface will not matter. Everything was working fine before reinstalling the server (CentOS). After I reinstalled it, the Plex Media Server did not work anymore.
The only thing I can deduce from this is a virtualization issue.
From here, I canāt tell you what it might be.
I can only see PMS is working.
I have no visibility into how you have the network topology or Centos configured.
At this point, I can only suggest you start backtracking and see what changed.
Walk through it from the beginning in your mind.
The server is configured by script, the only thing that changed was that it was with CentOS 7.4 and now it is with CentOS 7.6.
This server is the gateway / router of the network, so it has the networks 10.0.69 and 192.168.1 in it. This machine is a physical host, not a VM.
If the PMS is working properly, why does not it load the Media Server resource page correctly?
I thought it was simpler, something like:
# yum install plexmediaserver * .rpm && systemctl enable plexmediaserver && systemctl start plexmediaserver
And use firewall-cmd to free the access ports on all networks.
So it would work with my login. But that is not quite what is happening.
This server is hosted?
May 11, 2019 21:34:20.499 [0x7f5bb7a09780] DEBUG - * 8 vnet-external (192.168.1.2) (loopback: 0)
May 11, 2019 21:34:20.499 [0x7f5bb7a09780] DEBUG - * 9 vnet-internal (10.0.69.1) (loopback: 0)
May 11, 2019 21:34:20.499 [0x7f5bb7a09780] DEBUG - * 12 vnet-dmz (172.16.10.1) (loopback: 0)
No, it is a physical server in the company, where several services are executed, including the PMS.
You do realize Plex isnāt for commercial use?
You present an installation environment which we canāt support.
By āScripted installationā, we have no idea what might or might not be included in the runtime environment. It might not even be a publicly available kernel.
Plex is intended for private, non-commercial, use.
Exactly, it is not for commercial use. I am the only one that accesses PMS, it has been installed on this server and running for a long time. I use this server to develop products for my clients. Gives the need for multiple networks.
The kernel, libs, deps are all from CentOS 7.6.1810. There is nothing much on this server. The scripts are for a quick reconfiguration, in case I need to reinstall the server. I do not see where it can not be supported.
Would it be possible for me to obtain a copy of these configuration scripts?
The networking configuration I see in the logs is clearly not default naming.
I have no idea what else might have been done.
Networking is highly suspect given Plex/web on another computer canāt connect to the server in order to claim in.
The primary adapter having a public IP (as per RFC-1918),
requires SSH-Tunnel to get into it.
When this fails, there is little I can do without significantly more information about that configuration given is is not how Centos configures itself by default or by the typical user.
This is clearly the work of a firmās IT department.
How can I share server information with you?
Maybe by releasing access to the server? Would that help?
The network interfaces are bridge type over bonding, because this server has kvm services enabled (vnet-external -> Bonding only, vnet-internal -> Bridge over Bonding)
Ssh is configured to receive a high-port connection.
Audit, firewalld, and selinux are enabled.
What other information is important?
You said;
Would it be possible to see what this script does? (obtain a copy of it)
Hello, problem solved. Unconfigure SSH and I was able to execute the procedure to configure the PMS. Thank you all.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
