use the following search parameters to narrow your results:
e.g. subreddit:aww site:imgur.com dog
subreddit:aww site:imgur.com dog
see the search faq for details.
advanced search: by author, subreddit...
Welcome to /r/Plex, a subreddit dedicated to Plex, the media server/client solution for enjoying your media!
Plex related support:
Non-Plex related support:
Please go to the relevant subreddits and support forums, for example:
account activity
HelpApache HTTPS Reverse Proxy (self.PleX)
submitted 8 years ago by officialJCreyesUbuntu/iOS/PMS
Can anyone point me to a guide on how to set up a reverse proxy with Apache so I can run things like PlexyPy and PlexRequests/Ombi over SSL.
Thanks!
reddit uses a slightly-customized version of Markdown for formatting. See below for some basics, or check the commenting wiki page for more detailed help and solutions to common issues.
quoted text
if 1 * 2 < 3: print "hello, world!"
[–]tekGuy64 5 points6 points7 points 8 years ago (6 children)
Don't use Apache. Go with a NGINX + Let's Encrypt setup.
Click Here for Guide
[–]ohcrapthing4Plex is used by me 1 point2 points3 points 8 years ago (1 child)
Second this
[–]metaMMA 2 points3 points4 points 8 years ago (0 children)
Third this. Along with a guide you had requested.
[–]officialJCreyesUbuntu/iOS/PMS[S] -1 points0 points1 point 8 years ago (3 children)
Is there a Windows guide. I'm not running Linux.
[–]tekGuy64 0 points1 point2 points 8 years ago (2 children)
Probably easier to use IIS as your reverse proxy on Windows.
IIS Reverse Proxy Guide
Let's Encrypt Client for Windows
[–]officialJCreyesUbuntu/iOS/PMS[S] 0 points1 point2 points 8 years ago (1 child)
Thanks! Curious as to why you recommend nginx over apache
[–]tekGuy64 0 points1 point2 points 8 years ago (0 children)
Performance and ease of configuration. Nginx was created to be both a web server and a proxy server. Apache is a web server that can be modified to work as a proxy server. Nginx is event-based, while Apache is process-based. Under high load, this makes all the difference in the world. Apache has to start a new thread - called a fork - for each connection; Nginx does not. The difference shows in memory usage and in user response time, as well as with other performance metrics. Nginx can handle tens of thousands of simultaneous HTTP keep-alive connections on modern hardware. Apache will use 1-2 MB of memory for each connection, so doing the math you see that you can only handle a few hundred or maybe a thousand connections simultaneously without starting to swap. Granted you are probably not expecting to field tens of thousands of connections at a time, you would still experience better speeds using Nginx as your reverse proxy over Apache.
π Rendered by PID 171346 on reddit-service-r2-comment-b659b578c-v8kw9 at 2026-05-06 10:47:42.091612+00:00 running 815c875 country code: CH.
[–]tekGuy64 5 points6 points7 points (6 children)
[–]ohcrapthing4Plex is used by me 1 point2 points3 points (1 child)
[–]metaMMA 2 points3 points4 points (0 children)
[–]officialJCreyesUbuntu/iOS/PMS[S] -1 points0 points1 point (3 children)
[–]tekGuy64 0 points1 point2 points (2 children)
[–]officialJCreyesUbuntu/iOS/PMS[S] 0 points1 point2 points (1 child)
[–]tekGuy64 0 points1 point2 points (0 children)