These are network-related settings for your Plex Media Server. You can access these under Settings > Server > Network in Plex Web App.
Related Page: Using Plex Web App
Normal Settings
Secure connections
Choose how your Plex Media Server handles secure connections.
- Required – Only accept secure connections.
- Preferred – (Default) Accept and prefer secure connections when they’re available for a Plex app, but allow regular HTTP connections if the app doesn’t support secure connections or if one can’t be established.
- Disabled – Don’t allow Plex apps to connect securely and instead force all communication over regular HTTP.
Tip!: This setting is only available if your server is signed in to a Plex account. If you choose to set your Server to “Required”, then any Plex apps which don’t support secure connections won’t be able to connect. We recommend using the default “Preferred” setting.
Note: Even when set to “Required”, some internal requests originating from the Plex Media Server computer will still be over regular HTTP. This includes things like the plug-in framework, scanners, and DLNA server. These requests are only on the local machine itself.
Related Page: How to Use Secure Server Connections
Enable local network discovery (GDM)
Enable “G’Day Mate” discovery. This is used to allows Plex apps and Servers to find each other automatically on a local network.
Advanced Settings
Click on the Show Advanced button at the top right of the settings area to toggle display of advanced settings. Be careful when adjusting or using advanced settings.
Enable server support for IPv6
Enable IPv6 support.
Custom certificate location
The path plus filename to a PKCS #12 file that contains a certificate and private key to enable TLS support on a custom domain.
Custom certificate encryption key
The encryption passphrase used when creating the PKCS #12 certificate file being specified.
Custom certificate domain
The domain name being used for the custom certificate. It will be published to plex.tv using the port you currently have mapped under Settings > Server > Remote Access. The domain name must match a name in the custom certificate file.
Network Interface to listen on
For the benefit of users with multiple network cards and for systems such as NAS or Docker where there is always another network interface, which may get picked up by Plex Media Server, there is now the option to force Plex Media Server to use a specific network interface. The selected Network Interface will be used for local clients to use to connect to the server as well as the automatic mapping for uPnP port when Remote Access is enabled. (Requires Plex Media Server 1.13.5 or later)
Note 1: It is recommended that the selected IP Address is a DHCP Reserved IP or static outside DHCP Range (or both if within DHCP). If it does change, a restart is needed for Plex Media Server to bind to the new IP Address.
Note 2: In the event that the selected network interface is not available, Plex Media Server would then allow All interfaces to be used, but a restart would be needed to make Plex Media Server listen to the other IP Addresses
Remote streams allowed per user
You can set the maximum number of simultaneous streams each user is allowed to have, when not on the same network as the Plex Media Server (the “local” network).
Tip!: This feature requires an active Plex Pass subscription for the Plex Media Server admin Plex account.
LAN Networks
Very few people will need to set or change this preference. It simply lets you specify which IP addresses or networks will be considered to be “local” to you. If you set any bandwidth limits under Remote Access, those do not apply to “local” playback and only take effect for remote playback. By default, only the network subnet on which the server is located is considered to be “local” (which is appropriate for the vast majority of users).
Tip!: This feature requires an active Plex Pass subscription for the Plex Media Server admin Plex account.
Related Page: Server Settings - Bandwidth and Transcoding Limits
Treat WAN IP As LAN Bandwidth
This will be set by default. It allows incoming requests from this network’s WAN IP address to be treated as LAN requests in terms of bandwidth. This often occurs when DNS rebinding protection is in place and clients on the LAN cannot contact the server directly but instead have to go through the WAN IP address.
Custom server access URLs
A comma-separated list of URLs (either HTTP or HTTPS), which will be published to plex.tv for server discovery. This can be very useful in a few cases: if you’re using a VPN to get back home, if you’re using a reverse proxy in front of the media server, or if your networking configuration is otherwise unique. For instance, if you have your own custom domain with subdomain, you might add:
https://plex.mycustomdomain.com:32400Tip!: If you don’t specify a port, the port from your Remote Access page will automatically be used.
List of IP addresses and networks that are allowed without auth
The list of IP addresses or networks that can connect to Plex Media Server without authorization. Enter a comma-separated (no spaces or tabs!) list of IP addresses or specify a range using IP/netmask entries. This can be useful if you have an old, legacy, unsupported app (such as LG’s MediaLink or SmartShare apps) that you wish to use.
For instance, a value of 192.168.1.4,192.168.1.8 would allow devices at those two LAN IP addresses to connect to the server without authorization. Similarly, 192.168.1.100/255.255.255.0 uses a netmask to specify a range of local IP addresses. When the Plex Media Server is signed in to an account, specifying 127.0.0.1 will be ignored (you could instead use the specific LAN IP).
Tip!: Private/LAN addresses can be specified either as a range or as an individual IP address. Public addresses can only be specified as an individual IP address (using ranges/netmasks with public addresses will fail/be ignored).
Warning!: We strongly encourage using Plex apps that allow signing in to accounts to ensure the highest security for your computer and network.
Enable HTTP Pipelining
This feature can enable higher performance in the HTTP server component. A server restart is required for a change to take effect.
Webhooks
This feature can be enabled to allow your server to send events to external services.
Tip!: This feature requires an active Plex Pass subscription for the Plex Media Server admin Plex account
Related Page: Webhooks