nginxconfig.io VS Nginx Proxy Manager

Until recently I managed my instances like you -> file by file. With the help from the nginx config generator (now owned by digitalocean). Source: over 1 year ago

You would think when you select the Reverse Proxy option at nginxconfig.io, it would update the resolver info to work with that setup :(. Source: over 1 year ago

Please see my NGINX configuration (with the help of https://nginxconfig.io) in this pastebin. Source: over 1 year ago

If you want to be sure run your config through a tool like https://nginxconfig.io to see if it comes up with the same syntax. Source: almost 2 years ago

Thanks for the detailed overview! I'm realizing now it's significantly more than just plug and play thanks to the replies here. Using nginxconfig.io, I was able to get the reverse proxy working! I fail to fully load my web services once connected though - for example, they redirect to a login page, but its a blank screen - but they are accessible and secure from WAN! Source: almost 2 years ago

Take a look at NginxProxyManager. This would give you the opportunity to put everything in the form of service1.domain.com , service2.domain.com ,etc. Source: 4 months ago

So I'm going into the log folder and I'm getting this error. It started maybe a week ago. Some of my host will go through, but if the do, its super slow. Others just out right refuse. I've tried deleting nginx entirely and still comes to the same error. I had nginx running for a few months now, but this got started. To be clear, this is what I've been using https://nginxproxymanager.com/ . I don't know if there is... Source: 8 months ago

Hi! I am setting up a home server where I host a number of different services that I want to be accessible exclusively through a proxy (Nginx Proxy Manager). What I mean is that if I serve a website on port 8081, for example, and I try to browse to the server's IP and that port, I won't be able to find the website. Instead I will have to browse to the IP and port that the proxy I set up has configured for that... Source: 9 months ago

As far as website hosting, just set up a few Docker containers: one for a web-server of your choice, and one for a reverse proxy. I recommend Nginx Proxy Manager. It handles SSL certificates for you in a super simple way (both the initial acquisition process as well as auto renewal) and makes it easy to expand to using multiple web servers in the future, or setting up redirects without filling up your DNS records. Source: 9 months ago

I'm trying to set up Nginx Proxy Manager on an existing box. Since it's already set up with a few services I don't want to mess with, and a firewall I don't particularly want to migrate (nftables, a good solution that docker apparently doesn't play nice with), I turned off docker's iptables management (despite the warnings, yes). Source: 9 months ago