Custom server access URLs not respected (?)

General Discussions
1

I’ve setup the custom url to be https://plex.DOMAIN.com:443, I’ve got a properly working nginx reverse proxy working which presents the webui and everything as it should over HTTPS but when I try to play a stream - the stream goes over the https://plex.DOMAIN.com:32400 instead of https://plex.DOMAIN.com:443

sf6BxKG.png969×82

q3HWOFv.png901×839

Why is this? I’ve tried restarting and unpublish/publish the server a couple of the times without it helping

Both port 443 and 32400 is open in firewall

The log shows it connecting and publishing the url to plex

Jul 27, 2016 12:29:57.649 [0x7f6dbbbff700] DEBUG - HTTP requesting PUT https://plex.tv/devices/XXXXXXXXXXXXXXXXX?Connection[][uri]=https://plex.DOMAIN.com:443&Connection[uri]=https://plex.DOMAIN.com:32400&Connection[uri]=http://192.168.1.10:32400&Connection[uri]=http://172.17.0.1:32400&Connection[uri]=http://10.22.2.117:32400&httpsEnabled=1&httpsRequired=1&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Jul 27, 2016 12:29:57.908 [0x7f6dbbbff700] DEBUG - HTTP 200 response from PUT https://plex.tv/devices/XXXXXXXXXXXXXXXXX?Connection[][uri]=https://plex.DOMAIN.com:443&Connection[uri]=https://plex.DOMAIN.com:32400&Connection[uri]=http://192.168.1.10:32400&Connection[uri]=http://172.17.0.1:32400&Connection[uri]=http://10.22.2.117:32400&httpsEnabled=1&httpsRequired=1&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx

A wierd thing about these urls in the log is that 172.17.0.1 and 10.22.2.117 is old stuff, like months old?

2

Nobody? :frowning:

3

I’m not an expert in this area, but I believe the custom URL will use that same port that you specified for remote access. You can’t shortcut the port number by adding it to the custom URL setting. I don’t think it works that way.

4

@MovieFan.Plex said:
I’m not an expert in this area, but I believe the custom URL will use that same port that you specified for remote access. You can’t shortcut the port number by adding it to the custom URL setting. I don’t think it works that way.

Then consider this a bug report, your own documentation:

5

Just incase the dev’s want to test this, I’m using nginx 1.10.0 with this config

upstream plex {
server 192.168.1.10:32400;
}

	server {
		listen 192.168.1.10:443 ssl http2;

		server_name plex.domain.com;

		include domain.com.default.conf;

		access_log /var/log/nginx/domain.com/plex.domain.com-access.log;
		error_log  /var/log/nginx/domain.com/plex.domain.com-error.log;

		location / {
			# if a request to / comes in, 301 redirect to the main plex page.
					# but only if it doesn't contain the X-Plex-Device-Name header
			# this fixes a bug where you get permission issues when accessing the web dashboard
			if ($http_x_plex_device_name = '') {
				rewrite ^/$ http://$server_name/web/index.html;
			}

			# set some headers and proxy stuff.
			proxy_set_header X-Real-IP $remote_addr;
			proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

			# include Host header
			proxy_set_header Host $http_host;

			# proxy request to plex server
			proxy_pass https://plex;

			proxy_redirect off;
			proxy_buffering off;
			proxy_http_version 1.1;
			proxy_set_header Upgrade $http_upgrade;
			proxy_set_header Connection "upgrade";
			proxy_read_timeout 36000s;
		}
	}
6

I’ll bump this once again.