Dear all,

i would like to address my multiple cpu webservers through a single point of entry.
So i thought to set up a reverse proxy with my IOT2050 Adv. with the example image.
Installing nginx was no problem. The webserver itself is running.

What troubles me is the location section of the nginx config file.

I would like to do something like:

http://proxyip/cpu1 -> http://cpu1_web_ip/ 
http://proxyip/cpu2 -> http://cpu2_web_ip/

as described here​: https://serverfault.com/questions/854218/nginx-reverse-proxy-multiple-locations

But the solution given there does not work for me.
The best iteration was:

location /cpu1/ {
         rewrite /cpu1/(.*) /$1 break;
         proxy_pass http://cpu1_web_ip/;

}
Which gets me to the ​start page of the cpu webserver.
But the login to the webserver does not work.
Error: Not found.
Instead of taking me to proxyip/cpu1/FormLogin it takes me to proxyip/FormLogin

Any ideas?
Thanks in advance

​

Dear faschmidt,

I also tried it with the code descriped here:

https://serverfault.com/questions/854218/nginx-reverse-

I used: 

location ~ ^/cpu1(.*)$ {
proxy_pass http://cpu1-ip$1;
}

This takes me to http://proxyip/cpu1/FormLogin.

It shows "405 METHOD NOT ALLOWED".

This is also shown by accessing via cpu1-ip/FormLogin.

I doubt this message is your aim. Still, I hope this helps you with your task.

Best regards!

Thanks for the ideas.

In between time I choose another method on the nginx config.

I defined different server paragraphs where the server name differs between the cpu
webservers I like to address.
So my location is always /.
and the proxypass statement always refers to the ip of the webserver.

Now you only have to set the headers correct and everything works just fine.

The working headers can be found here:

Reverse Proxy — Kasm 1.8.0 documentation (kasmweb.com)

Note that KASM has nothing to do with the solution. But the header correction just
magically works. I did not fully understand, why and if everything there is needed.

The only downside is to have a name resolution and therefore a DNS in the outer net
just to resolve something like https://cpu1iot2050 to the IP of the reverse proxy that then
checks for the correct server string.

Simplest way is the hosts file on the device that wants to use the proxy.

If I get time I do a complete guide for this. 

Hi. :)

I want to achieve something similar, so may I ask for your nginx configuration file as an example?