The error /usr/share/nginx/html/site1" failed (2: No such file or directory) suggests your location block isn't being matched at all and nginx is trying to serve a file instead, the reason why is hard to say without seeing the rest of the config.
Even if it did work, because you are using /site1 nginx will proxy the request to localhost:9966/site1 as well. This might not be what you want and in general running something in a subfolder complicates things a lot.
Thanks for your respons. Maybe what I want to do is not possible, or not how nginx work.
I will be running several different applications on the same server from different ports.
If i run localhost:9966 in my browser I get to the application as i want. But I want to reach it when i go to localhost:8000/app1 Another application will respond on localhost:8000/app2 and so on.
I did manage to get upstream to be localhost:9966/site1 when I hit localhost:8000/site1. But I was hoping that would proxy to localhost:9966 and not localhost:9966/site1
The error
/usr/share/nginx/html/site1" failed (2: No such file or directory)
suggests your location block isn't being matched at all and nginx is trying to serve a file instead, the reason why is hard to say without seeing the rest of the config.Even if it did work, because you are using /site1 nginx will proxy the request to localhost:9966/site1 as well. This might not be what you want and in general running something in a subfolder complicates things a lot.
Thanks for your respons.
Maybe what I want to do is not possible, or not how nginx work.
I will be running several different applications on the same server from different ports.
If i run localhost:9966 in my browser I get to the application as i want. But I want to reach it when i go to localhost:8000/app1 Another application will respond on localhost:8000/app2 and so on.
I did manage to get upstream to be localhost:9966/site1 when I hit localhost:8000/site1. But I was hoping that would proxy to localhost:9966 and not localhost:9966/site1
More replies More replies