Website.com VS Nginx Proxy Manager

Yeah, def seeing https://website.com and website.com and www.website.com, etc, being treated as "different" urls which means its a nice way to add just a little bit more load to servers. - Source: Hacker News / 3 months ago

I just tried a www.website.com test and pinged www.website.com and got no results. I then pinged website.com and received results coming back from www3.website.com. So it does matter how the redirecting resolves. Source: 5 months ago

I made a website using the seedprod editor on wordpress. I setup a URL before switching to seedprod. I am apparently forced to use a /'abcde' after .com in my URL. Going to the website using the website name ending in .com doesn't bring you to the seedprod page, it brings you to the unedited/unused original wordpress filler text/template. Is there anyway I can get it to let me just use the website.com instead of... Source: 9 months ago

I know some websites that are mobile have a m.website.com and some websites just have website.com. Source: 10 months ago

It may be more cumbersome if you’re trying to get more people than just people you directly know to visit, but there may also be a dns service to redirect a http://website.com to http://ipaddress:8090 so your IP isn’t being handed out willynilly. Source: 10 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