in your upstream configuration you have ports defined ( 6666 and 9999 ), those are the ports your backend servers need to listen on the proxy_pass directive doesn’t need an additional port configuration in this case. Your nginx listens on port 81 which you’ve defined in the listen directive Is this what you tried to … Read more
Add the following code to your Nginx Config, as detailed in the VueRouter docs, here: location / { try_files $uri $uri/ /index.html; } Also, you need to enable history mode on VueRouter: const router = new VueRouter({ mode: ‘history’, routes: […] })
References to nginx docs: HttpCoreModule#location, HttpProxyModule#proxy_pass. There is a better way than using regex (which is slow) for location match. In this case, you could use ^~ to tell nginx to match the given prefix /mail before doing any regex match. You also don’t need that rewrite rule because proxy_pass can do that simple rewrite … Read more
You can create a ConfigMap object and then mount the values as files where you need them: apiVersion: v1 kind: ConfigMap metadata: name: nginx-config data: nginx.conf: | your config comes here like this other.conf: | second file contents And in you pod spec: spec: containers: – name: nginx image: nginx volumeMounts: – name: nginx-config mountPath: … Read more
I finally found the solution: I need to pass $request_uri parameter : location / { proxy_pass http://tracking/webapp$request_uri; } That way, characters that were encoded in the original request will not be decoded, i.e. will be passed as-is to the proxied server.
There are two ways I know you could solve this problem. Allow-list in separated config: Works on all common NginX installs You can place all of the allow statements in a simple text file, per site, that contains nothing but allow statements. Include that under the client’s server block. Use scripts as needed to alter … Read more
The proxy_set_header HEADER “” does exactly what you expect. See https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_set_header. If the value of a header field is an empty string then this field will not be passed to a proxied server: proxy_set_header Accept-Encoding “”; I have just confirmed this is working as documented, I used Nginx v1.12.
In case if somebody is still looking for the answer. jwilder/nginx-proxy allows you to use custom Nginx configuration either a proxy-wide or per-VIRTUAL_HOST basis. Here’s how can you do it with Per-VIRTUAL_HOST location configuration. Inside your poject folder create another folder – “vhost.d”. Create file “whoami.local” with custom nginx configuration inside “vhost.d” folder. This file … Read more
No, they are not needed if you define your server blocks properly in nginx.conf, but it’s highly suggested. As you noticed, they are only used because of the include /etc/nginx/sites-enabled/*; in nginx.conf. For curiosity, is there a reason why you do not want to use them? They are very useful; easier to add new sites, … Read more