my product VS Nginx Proxy Manager

[general] Duration = 0 # Stream indefinitely BufferSecs = 5 # Buffer for the input, in seconds Reconnect = yes # Reconnect to the server if disconnected [input] Device = default # Your audio capture device SampleRate = 44100 # Sample rate in Hz BitsPerSample = 16 # Bits per sample Channel = 2 # 2 = stereo, 1 = mono [icecast2-0] BitrateMode = cbr # Constant bit rate Format = mp3 # Audio format Bitrate = 128 #... - Source: dev.to / 5 days ago

It’s frustrating that even on notion paid plans, the best you can do is a notion.site subdomain like mywebsite.notion.site. Why can’t I just connect to mywebsite.com? Source: 7 months ago

I made more or less progress by adding the PathPrefixes to my router but it can't be the correct way to handle this as it could interfer with the service I host on the root of https://mywebsite.com . Source: 8 months ago

Var req = require('request')req("http://mywebsite.com", function(err, resp, body) { var output = // pull some interesting pieces out of the whole body console.log(output);}); The generation of my output variable is not central to the issue here. The relevant parts are that I use request to make an asynchronous call and use console.log to output my results... Maybe this is a problem? Source: 10 months ago

Mywebsite.com/?landing-facebook is what I'm attempting, but this takes me to mywebsite.com and not the mywebsite.com/landing page. 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: 10 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