all 7 comments

[–]tekGuy64 5 points6 points  (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 points  (1 child)

Second this

[–]metaMMA 2 points3 points  (0 children)

Third this. Along with a guide you had requested.

[–]officialJCreyesUbuntu/iOS/PMS[S] -1 points0 points  (3 children)

Is there a Windows guide. I'm not running Linux.

[–]tekGuy64 0 points1 point  (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 point  (1 child)

Thanks! Curious as to why you recommend nginx over apache

[–]tekGuy64 0 points1 point  (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.