3

<Location /api> is not ignored, you just haven't configured the authentication for it, so the configuration from the higher level applies. Disable AuthType for the location: <Location /api> AuthType None Require all granted ProxyPass http://localhost:90/ ProxyPassReverse http://localhost:90/ </Location>


2

You can use the listen directive multiple times in the server block Sample Config server { listen 1.1.1.1:80; listen 1.1.1.2:80; listen 1.1.1.3:80; server_name proxy.site.net; proxy_pass https://example.com/ }


2

First of all, I think it's important to understand a little background on how CORS works: CORS is validated client-side by the browser. To verify that an origin (different domain, protocol or port) is allowed to access another origin a pre-flight request may be issued before the actually Cross-Origin request. This request uses the OPTIONS method and needs ...


2

As said above it can be solved by proxy_set_header Authorization "Basic dXNlcjpwYXNzd29yZA=="; where dXNlcjpwYXNzd29yZA== is result of command: echo -n "user:password" | base64 i guess you already tried that anyway, i believe correct location will looks like location / { proxy_set_header Host $host; proxy_set_header X-Real-IP $...


2

Instead of having Apache do that leg work, have NGINX do it before it even hands off the data to Apache by setting the Host header that Apache is expecting as part of the proxy_pass handoff with an extra configuration option. NGINX has the following variable for proxy_set_header to augment what is passed to the proxy in the backend. So you'd have something ...


2

I don't see why you would need iptables over here. Just install a server as a reverse proxy, have that server's IP in the whitelisted IPs. End-users will connect to that server, which will reverse proxy connections to the final destination. A reverse proxy opens a connection from its own IP address to the proxied server IP address, so you don't need any ...


1

Get a different professional ISP service that supports opening ports. An ISP that does not allow a http server is not going to be helpful troubleshooting remote access to your network. Or host the web server remotely, not on your LAN. Many hosting providers to choose from.


1

Traefik doesn't know which IP of the container it should try to connect. You're close with traefik.docker.network=web but that's not really the name of the network. The network will get a prefix for the project or stack name. To hard code the network name, you can use the name field in the final network section (this is specific to version 3.5 or newer): ...


1

I solved this issue by defining a new environment variable called APP_HOST in the Google Cloud Run control panel and setting it to example.com. Then I added the following configuration to the .htaccess file in the document root: <IfModule mod_env.c> PassEnv APP_HOST </IfModule> <IfModule mod_headers.c> RequestHeader set Host %{...


1

I wrote this answer on the topic on Stack Overflow and it’s still pretty relevant. The benefits of HTTP/2 (and HTTP/3) are primarily for the front end. You’re unlikely to see any real, noticeable benefits over the back end. And, given support is often lacking for these newer protocols I wouldn’t lull myself to enable it with so few gains. The one interesting ...


1

As far a I know ssl_preread directive works only with HTTPS protocol. I don't know how to get HTTP Host header value in the ngx_stream_core_module. You can try to use an additional server block in the http context like shown here: http { ... map $http_host $proxy { hostnames; .neverssl.com $http_host; ... } server {...


1

Edit with Amcrest-specific solution At some point (around 2017?) Amcrest released a firmware update that removed Basic Authentication from their IP cameras, leaving Digest Authentication as the only option. This Stack Overflow answer may be your best option for stripping the Digest Authentication out like you want using FastCGI and nginx. Either that or ...


1

Is it ok to use Nginx in the host which will forward traffic to multiple different dockerized Nginx? Yes. This is one way to do it. Does it have any known problems? The host instance of NGINX is not containerised which may make it more difficult to configure. Another common way to do this is to have a docker container bound to port 80 and 443 which handles ...


1

Is it ok to use Nginx in the host which will forward traffic to multiple different dockerized Nginx? Yup, it's actually a common practice. Does it have any known problems? Caused by this setup itself - nope. Will that affect performance? In a way - sure: like every other load balancer (which it is) it will add some delay on buffering and TCP sockets.


Only top voted, non community-wiki answers of a minimum length are eligible