QAbc VS Nginx Proxy Manager

I need to switch up really soon to a xyz.com domain, obviously abc.com can remain up as alias for 1 - 2 years, and the idea is to keep receiving as abc.com but to start sending as xyz.com. Source: 11 months ago

I know I could modify our internal DNS server and point domain abc.com to 127.0.0.1. Source: 11 months ago

Anyone having weird robot sound artifacts from the abc.com stream? Source: 11 months ago

So I have a 20 year old e-commerce site with good rankings. I'm having an entirely new site created. I don't want to give my developer access to the existing site (i.e. abc.com). What are the consequences of having him build the new site at abc.net and then in the future forwarding .com to the .net. I'd prefer the .com to always be the real access name (in rankings, search and bookmarks) but the workings of the... Source: 11 months ago

And I went to abc.com, and I see the F1 race with a "Live Now", and when I click it, I got some ABC News Live channel. None of their other channels listed are airing it either. Frustrating. Curious what affiliate you are watching on? Source: 11 months 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: 5 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: 9 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: 10 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: 10 months ago