Hello,
I recently installed plex on my Debian 10 server but sadly cannot access its plex webpage. I’m not that great at network so I probably configured it wrong. But I can’t figure out where I messed.
I (tried to) configured subdomains and http -> https redirection (certificate provided by certbot). I’m using the following vhosts :
plex-le-redirect.conf :
<VirtualHost *:80>
ServerName media.hijackedbrain.com
ServerSignature Off
RewriteEngine On
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
ErrorLog /var/log/apache2/redirect.error.log
LogLevel warn
</VirtualHost>
plex.conf :
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerName media.hijackedbrain.com
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyRequests Off
ProxyPreserveHost On
ProxyPass / https://hijackedbrain.com:32400/
ProxyPassReverse / https://hijackedbrain.com:32400/
RewriteEngine on
RewriteCond %{REQUEST_URI} !^/web
RewriteCond %{HTTP:X-Plex-Device} ^$
RewriteRule ^/$ /web/$1 [R,L]
SSLCertificateFile /etc/letsencrypt/live/hijackedbrain.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/hijackedbrain.com/privkey.pem
</VirtualHost>
</IfModule>
But whenever I try to access the plex webpage, it gives me a 503 error and print this into apache2’s error log :
[Sat Aug 03 19:08:46.843994 2019] [proxy:error] [pid 12082] (111)Connection refused: AH00957: HTTPS: attempt to connect to 163.172.82.14:32400 (hijackedbrain.com) failed
[Sat Aug 03 19:08:46.844053 2019] [proxy_http:error] [pid 12082] [client 178.18.61.242:55100] AH01114: HTTP: failed to make connection to backend: hijackedbrain.com
[Sat Aug 03 19:08:47.414056 2019] [proxy:error] [pid 12081] (111)Connection refused: AH00957: HTTPS: attempt to connect to 163.172.82.14:32400 (hijackedbrain.com) failed
[Sat Aug 03 19:08:47.414116 2019] [proxy_http:error] [pid 12081] [client 178.18.61.242:55101] AH01114: HTTP: failed to make connection to backend: hijackedbrain.com
So I’m guessing I did something wrong with ProxyPass but what exactly ? Thanks to whoever spent 2 minutes reading this. And more thanks if you’re responding.
EDIT : tldr version of this thread. Somehow the .deb didn’t install correctly. Thus the installation was corrupted, and the server wasn’t running at all … So it wasn’t a vhosts issues at all. I had to to use a beta build of the installer (linked in messages below) to install it on debian 10 somehow. Once it was up and running everything was dandy and fine.
Server Version#: latest 1.16.3.1402-22929c8a2 - July 15, 2019
Player Version#: none