Hi guys. I too have had this working just fine and after upgrading to fedora 20 I am getting 503 service unavailable. Has anything changed from apache 2.2 to 2.4 that would affect this? All my other reverse proxies still work except plex.
With the most recent version of plex, here are the added items that are needed to make it work. Hope others may find it useful.
ProxyPass http://localhost:32400/web ProxyPassReverse http://localhost:32400/web<Location /system>
ProxyPass http://localhost:32400/system
ProxyPassReverse http://localhost:32400/system
<Location /servers>
ProxyPass http://localhost:32400/servers
ProxyPassReverse http://localhost:32400/servers
<Location /accounts>
ProxyPass http://localhost:32400/accounts
ProxyPassReverse http://localhost:32400/accounts
<Location /myplex>
ProxyPass http://localhost:32400/myplex
ProxyPassReverse http://localhost:32400/myplex
<Location /photo>
ProxyPass http://localhost:32400/photo
ProxyPassReverse http://localhost:32400/photo
<Location /clients>
ProxyPass http://localhost:32400/clients
ProxyPassReverse http://localhost:32400/clients
Does this still work with the current version of PMS?
Could someone please post a complete working vhost config?
hi, the ananke's solution is good but this one is better because it doesn't depends on Plex's url/locations. Also Plex is getting it's sections using the root (http(s)://your-ip/) so if you are not using it from your local network the ananke's solution won't work.
Read here: http://adrhc.asuscomm.com/ffp_0.7_packages/plex-apache.html and apply step 1 then 2 to ananke's solution too if you insist on using it.
If you are not using a storage similar to Zyxel nsa310 than use the configuration specified as "valid for non-Zyxel users too".
I know that most of this topic uses apache as a solution to this issue. I was able to setup a configuration in IIS with Application Request Routing and reverse proxy to access Plex externally over SSL with https://mydomain.com/plex
I wrote a 16 step description of how I got the configuration to work: https://forums.plex.tv/topic/92623-how-to-setup-iis-with-plex/#entry693352
Maybe a bit late but got my apache proxypass working using this
my plex is now running at https://host/plex/
Here is my working config with apache 2.2.22
Address format: plex.hostname.com
I used hostname instead of localhost in the ProxyPass to be able to use Plex authentication for login.
ServerName plex.hostname.com<Proxy *> Order deny,allow Allow from all </Proxy> ProxyRequests Off ProxyPreserveHost On ProxyPass / http://hostname.com:32400/ ProxyPassReverse / http://hostname.com:32400/ RewriteEngine on RewriteCond %{REQUEST_URI} !^/web RewriteCond %{HTTP:X-Plex-Device} ^$ RewriteRule ^/$ /web/$1 [R,L]
Hello there,
i know this topic is quite old, but i am also working on this solution.
My actual "problem" is that after i start a session in my browser to my reverse proxy, plex is always presenting me the login page.
I configured plex with disableRemoteSecurity and allowedNetworks not to ask for any credentials. This works in my local network.
And as far as myunderstanding is, a reverse proxy is a client in my local network towards plex server. So i do not know why it asking for them.
I tried with allowedNetworks 127.0.0.1/255.255.255.255,192.168.x.x/255.255.255.255 or simply 0.0.0.0/0.0.0.0, but it does not matter.
I do ssl and auth against my reverse proxy so i do not really a second auth.
Does somebody has this configuration without the login page from plex?
By the way i use apache 2.4.10 on windows with plex 0.9.11.7.
If i should post my question in a new thread under Windows, just tell me.
Best Regards,
kaniggl
I am using Ubuntu 14.04 64 bit. I installed Plex server but I am getting 404 Not Found on http://127.0.0.1:32400/web/index.html. I am also using apache 2.4.7 and I suspect that it is conflicting with the Plex server configurations. Can somebody help?
I would rather say that the plexemediaserver service is not started or not listening on 32400 than there is an apache issue.
Please check that plexmediaserver is started. You may use service plexmediaserver status to do that.
If it is started, list all listening ports and search for 32400 or one related to plex. You may use ss -ltp to list opened ports.
If plex is not listening on port 32400, then your 404 is fully explained.
If plex listen on port 32400, try connect via http://localhost:32400/web
Maybe a bit late but got my apache proxypass working using this
my plex is now running at https://host/plex/
I was using this last night for 6 hours or so and it was working great, when I woke up this morning, this stopped working and it can no longer connect to the plex server, even though the web interface is still up and running and usable.
@kaniggl said:
Hello there,i know this topic is quite old, but i am also working on this solution.
My actual “problem” is that after i start a session in my browser to my reverse proxy, plex is always presenting me the login page.
…
I tried with allowedNetworks 127.0.0.1/255.255.255.255,192.168.x.x/255.255.255.255 or simply 0.0.0.0/0.0.0.0, but it does not matter.I do ssl and auth against my reverse proxy so i do not really a second auth.
I’m having the same issue. Have you ever solved this?
I’m updating this thread in case anyone with a newer version of PMS is trying this out. I currently have a subdomain serving Plex via only HTTPS, with the standard port 32400 inaccessible remotely. It is still available via port 32400 on my local network (although I may disable this at some point).
Plex settings:
Remote Access:
Remote Access enabled
Manually specified public port: 443
My server shows the error Not available outside your network, but this is not the case. I’m not sure why this displays.
Network:
Secure connections: Disabled
Custom server access URLs: https://plex.mydomain.com:443
HTTPS is handled by the Apache proxy; this could also be terminated in Plex if you want to use HTTPS on your local network via port 32400. However, you would then need to populate the custom certificate fields and manage the key for your subdomain. I found it much easier to let the proxy do it all for me (and it works well with LetsEncrypt).
Apache conf:
<VirtualHost *:80>
ServerName plex.mydomain.com
Redirect permanent / https://plex.mydomain.com/
</VirtualHost>
<VirtualHost *:443>
ServerName plex.mydomain.com
SSLEngine On
# Some server hardening
SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
Header always set Strict-Transport-Security "max-age=63072000; includeSubdomains; preload"
# Enable proxy (for reverse-proxying)
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyRequests off
ProxyPreserveHost on
SSLProxyEngine on
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
# LetsEncrypt certs
SSLCertificateFile /etc/letsencrypt/live/mydomain.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/mydomain.com/privkey.pem
AllowEncodedSlashes NoDecode
# Finally, the Plex reverse-proxy
ProxyPass / http://localhost:32400/
ProxyPassReverse / http://localhost:32400/
</VirtualHost>This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
