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: 10 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: 11 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: 11 months ago

Unfortunately, the API we created is not suitable for anything but the most basic prototyping. For a real API, we will likely want to use our own domain. This appears to be quite complicated in GCP. We will need a Load Balancer, a serverless NEG and an API Gateway among some other components. See Getting started with HTTP(S) Load Balancing for API Gateway and HTTP(S) Load Balancing for API Gateway. - Source: dev.to / over 1 year ago

Set up a Load Balancer and Cloud Armor in front of your function, or. Source: over 1 year ago

In this article, I’ll show you how to configure a global cloud load balancer that serves as both a proxy and a load balancer. This type of load balancer comes with a single IP address that can be accessed from any location on earth and can route a request to the nearest (active!) application instance. - Source: dev.to / over 1 year ago

Cloud Load Balancing for distribution. - Source: dev.to / almost 2 years ago

While the precise features of the application are immaterial, the architecture is of primary importance. A lot of tools (and buzzwords) come to mind when trying to architect a modern web application. Assets can be served from a CDN to improve page load speed. A global load balancer can front all traffic, sending requests to the nearest server. Serverless functions and edge functions can be used to handle requests,... - Source: dev.to / almost 2 years ago