These are network-related settings for your Plex Media Server. You can access these under Settings > Server > Network in Plex Web App.
Related Page: Plex Web App
Normal Settings
Enable local network discovery (GDM)
Enable “G’Day Mate” discovery. This is used to allows some 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.
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.
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. This is not advised. We strongly 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 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.
Preferred network interface
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 Plex client applications may try to use to connect to the Plex Media Server, there is the option to ignore the extra interfaces and for users to select a specific interface that Plex Media Server would announce to plex.tv thus ensuring local Plex clients would only try that interface. (Requires Plex Media Server 1.13.9 or later.)
Note: A restart of Plex Media Server is required for a change in the settings to take effect.
Warning: If you have Remote Access enabled and are having Plex automatically map the port (as opposed to specifying a port manually), then Plex Media Server has no control over which network interface is used for an automatically-mapped port. Thus, it’s possible that Remote Access connections could come through an interface other than the one specified here.
Strict TLS configuration
If this setting is enabled, it prevents Plex Media Server from using or accepting the deprecated TLSv1.0 and v1.1 protocols, as well as legacy weak ciphers. May prevent older clients from connecting. The vast majority of users will have no reason to enable this option (and receive no benefit from doing so).
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. Addresses can be specified either as an individual IP address or a range (using IP/netmasks). Do not include spaces or tabs.
Related Page: Server Settings - Bandwidth and Transcoding Limits
Terminate Sessions Paused for Longer Than
You can instruct the server to automatically terminate playback sessions that remain paused for longer than the specified duration (where the value is the number of minutes). This does not affect audio-only sessions or Live TV streams. The default of 0 (zero) means the server will not automatically terminate such paused sessions.
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.
Enable Relay
You can, optionally, disallow the use of our “Relay” service. The Relay allows connections to the server through a proxy relay when the server is not accessible otherwise. Relay connections are bandwidth limited. See the related article for more details about “Relay”. The vast majority of users will have no reason to disable this option.
Related Page: Accessing a Server through Relay
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 (WAN) addresses are not valid for this server setting. Do not include spaces or tabs.
Warning!: Any app connecting to the server this way without being signed in will be treated as the admin/owner. That means access to all libraries as well as the ability to change server settings. We strongly encourage using Plex apps that allow signing in to accounts to ensure the highest security for your computer and network.
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