Server Version#: Windows Server 2016
Plex Server: 1.13.5.5332
In our studio we are running Plex on a dedicated Windows Server 2016 machine behind NAT - all LAN clients will have a 192.168.0.0/24 IP.
The Windows Server’s default adaptor is listening on 192.168.0.100.
We use hyper-v to run VM’s and have a vethernet adaptor for it. The default IP address for the vethernet adaptor is 192.168.0.50. Each VM has its own LAN IP address.
In Plex > Server > Network > Network interface to listen on, we see the following options:
ALL
Ethernet (192.168.0.100)
vEthernet (192.168.0.50)
Selecting “Ethernet (192.168.0.100)” will stop Plex server from listening on 127.0.0.1 but when double clicking the tray icon, it will try to load http://127.0.0.1:32400/web/index.html but times out since Plex stops listening on that interface. Plex can be accessed via 192.168.0.100, however, it will not scan new media files.
The log files show that it still tries to do curl/API requests to 127.0.0.1. If the ethernet adaptor/IP address is changed, Plex should then use that address for all requests. It wouldn’t make sense to still use 127.0.0.1 unless Plex will always listen on 127.0.0.1 regardless of which adaptor is selected. I would prefer if Plex would always listen on the loopback interface regardless of which adaptor is selected.
I’m not sure if this was a bug recently introduced but it can be replicated on any windows server system with multiple adaptors. I understand the large majority of issues posted on the forums are not issues with Plex but down to individual use but this is a bug so hopefully it can be escalated to the relevant people with haste.
Thank you.
