# Custom server access URLs not respected (?)

**URL:** https://forums.plex.tv/t/custom-server-access-urls-not-respected/152859
**Category:** General Discussions
**Created:** [July 27, 2016, 10:33am UTC](https://forums.plex.tv/t/custom-server-access-urls-not-respected/152859 "2016-07-27T10:33:05Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![jkaberg](https://avatars.discourse-cdn.com/v4/letter/j/90db22/32.png) [@jkaberg](https://forums.plex.tv/u/jkaberg)
#### Post date: [July 27, 2016, 10:33am UTC](https://forums.plex.tv/t/custom-server-access-urls-not-respected/152859/1 "2016-07-27T10:33:05Z")

</div>

I’ve setup the custom url to be [https://plex](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](https://plex). **DOMAIN**.com:32400 instead of [https://plex](https://plex). **DOMAIN**.com: **_443_**

 ![](https://i.imgur.com/sf6BxKG.png)

 ![](https://i.imgur.com/q3HWOFv.png)

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](https://plex.tv/devices/XXXXXXXXXXXXXXXXX?Connection%5B%5D%5Buri%5D=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](https://plex.tv/devices/XXXXXXXXXXXXXXXXX?Connection%5B%5D%5Buri%5D=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?

---

<div class="post-metadata">

### Author: ![jkaberg](https://avatars.discourse-cdn.com/v4/letter/j/90db22/32.png) [@jkaberg](https://forums.plex.tv/u/jkaberg)
#### Post date: [July 28, 2016, 6:41am UTC](https://forums.plex.tv/t/custom-server-access-urls-not-respected/152859/2 "2016-07-28T06:41:31Z")

</div>

Nobody? ☹

---

<div class="post-metadata">

### Author: ![anon18523487](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@anon18523487](https://forums.plex.tv/u/anon18523487)
#### Post date: [July 29, 2016, 8:05am UTC](https://forums.plex.tv/t/custom-server-access-urls-not-respected/152859/3 "2016-07-29T08:05:00Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![jkaberg](https://avatars.discourse-cdn.com/v4/letter/j/90db22/32.png) [@jkaberg](https://forums.plex.tv/u/jkaberg)
#### Post date: [July 29, 2016, 6:10pm UTC](https://forums.plex.tv/t/custom-server-access-urls-not-respected/152859/4 "2016-07-29T18:10:24Z")

</div>

> @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:

![](https://jkaberg.com/upload/screenshot/chrome_2016-07-29_20-09-21.png)

---

<div class="post-metadata">

### Author: ![jkaberg](https://avatars.discourse-cdn.com/v4/letter/j/90db22/32.png) [@jkaberg](https://forums.plex.tv/u/jkaberg)
#### Post date: [July 30, 2016, 1:26pm UTC](https://forums.plex.tv/t/custom-server-access-urls-not-respected/152859/5 "2016-07-30T13:26:44Z")

</div>

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;
> }
> }
> 
> ```

---

<div class="post-metadata">

### Author: ![jkaberg](https://avatars.discourse-cdn.com/v4/letter/j/90db22/32.png) [@jkaberg](https://forums.plex.tv/u/jkaberg)
#### Post date: [August 15, 2016, 2:23am UTC](https://forums.plex.tv/t/custom-server-access-urls-not-respected/152859/6 "2016-08-15T02:23:46Z")

</div>

I’ll bump this once again.

---

<div class="post-metadata">

### Author: ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)
#### Post date: [January 7, 2020, 9:41pm UTC](https://forums.plex.tv/t/custom-server-access-urls-not-respected/152859/7 "2020-01-07T21:41:14Z")

</div>


