command line magic<\/a> I got plex to work, I no longer need plex:32400/web<\/p>\nThank you!<\/p>\n
RewriteEngine on\nRewriteCond %{REQUEST_URI} !^/web\nRewriteCond %{HTTP:X-Plex-Device} ^$\nRewriteRule ^/$ /web/$1 [R,L]\n<\/code><\/pre>","upvoteCount":0,"datePublished":"2016-08-16T22:40:39.000Z","url":"https://community.spiceworks.com/t/best-practices-with-reverse-proxy/518053/9","author":{"@type":"Person","name":"techtornado","url":"https://community.spiceworks.com/u/techtornado"}},{"@type":"Answer","text":"Just to follow up, I found some time and now working through the quirks of setting up SSL.
Right now, direct HTTPS from Cloudflare to the server - works perfectly.HTTPS to the Proxy all falls apart with a descriptive error (on par with Windows 10 Something Happened)
Will research later, work in progress, learning much from this experience.<\/p>","upvoteCount":0,"datePublished":"2016-08-31T00:22:37.000Z","url":"https://community.spiceworks.com/t/best-practices-with-reverse-proxy/518053/10","author":{"@type":"Person","name":"techtornado","url":"https://community.spiceworks.com/u/techtornado"}},{"@type":"Answer","text":"
When you’re using a reverse proxy, you want your certs and private keys on the proxy server, not the webserver. It sounds like, from your description, the certs are on the webserver.<\/p>\n
The 500 error most likely indicates an apache config error. Try this command on both the webserver and the proxy:
Network info:
Cloudflare is doing the heavy lifting of DNS and protection from the bad actors across the web.
Right now, I’m forwarding port 80 to access the main site and it works wonderfully, but expansion to other sites are limited now.
I read that a reverse proxy will direct the web request to the correct server based on the header request it reads.
Is that still the best practice?
2 Spice ups
I personally use a reverse proxy to host a few sites from my home.
1 Spice up
Cool, I do like ubuntu, and I’ll start testing out Apache mod_proxy soon.
Now to find a setup/configuration guide that uses good pictures…
Thank you for your help Dave!
No pictures needed, my friend.
Here’s a decent guide to get you started:
The guide uses the aptitude package manager. I tend to just use apt . To do that just replace the aptitude command with
everything else should be the same.
Do yourself a favor and use SSL on your sites!
Let's Encrypt is a free, automated, and open certificate authority brought to you by the nonprofit Internet Security Research Group (ISRG). Read all about our nonprofit work this year in our 2023 Annual Report.
SSL is a work in progress, will check that out soon. I ran into issues, I followed the DigitalOcean guide and I’m not sure it worked on my server.
Substituted aptitude for apt-get and it says libapache2-mod-proxy-html not found.
Whenever I change out the main webserver for the proxy server, the browser lands on the Apache2 Testpage, so I’m not sure the reverse part of the proxy is working yet.
I can reset the VM and start over, but is there a better guide to use that has the right proxy package in apt-get?
You don’t have to start over! If your getting the Apache test page that means apache is working you just have some config work left.
Feel free to ‘obfuscate’ your specific domain name unless you want some extra traffic to your sites, haha.
Haha! My sites aren’t ready for live access yet.
One is a photo gallery I have yet to build, and the other is plex, so redirecting that request on port 80 to 32400 may need to be done.
Here’s my config with changed IP and domains.
Listen 80
<VirtualHost 10.0.0.10:80>http://10.0.0.10:80/ http://10.0.0.10:80/ example.com
<VirtualHost 10.0.0.15:80>http://10.0.0.15:32400/ http://10.0.0.15:32400/ plex.example.com
<VirtualHost 10.0.0.20:80>http://10.0.0.10:80/ http://10.0.0.10:80/ example2.com
So the first thing that pops out to me is that you are defining your virtual hosts with internal IP addresses.
Try changing each virtual host to
VirtualHost *:80
[edit]
The *:80 worked!
And with some command line magic I got plex to work, I no longer need plex:32400/web
Thank you!
RewriteEngine on
RewriteCond %{REQUEST_URI} !^/web
RewriteCond %{HTTP:X-Plex-Device} ^$
RewriteRule ^/$ /web/$1 [R,L]
Just to follow up, I found some time and now working through the quirks of setting up SSL.
Right now, direct HTTPS from Cloudflare to the server - works perfectly.HTTPS to the Proxy all falls apart with a descriptive error (on par with Windows 10 Something Happened)
Will research later, work in progress, learning much from this experience.
When you’re using a reverse proxy, you want your certs and private keys on the proxy server, not the webserver. It sounds like, from your description, the certs are on the webserver.
The 500 error most likely indicates an apache config error. Try this command on both the webserver and the proxy:
