Hello @pokoli
I had similar issue using flask_tryton but I solved with gunicorn and SCRIPT_NAME param, I saw this : uwsgi protocol magic variables — uWSGI 2.0 documentation and seems that uwsgi has something similiar uwsgi_param SCRIPT_NAME /testapp;
Do you think this could apply to SAO also? sao use uwsgi or… not possible in that way. Just asking 
No, his is unrelated. Sao neeed to be adapted (as well as tryton) because they manage to build the correct url when deployed on a subpath. That’s why I created the issue.
Hi! I am facing same issue. My nginx configuration goes:
location / {
root /srv/www/htdocs;
index index.html index.htm;
}
location /tryton/ {
proxy_pass http://localhost:8000/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $server_name;
}
I can see the tryton login, but once I tried to log on it gave me the ‘not found’ error message. There is something missing on nginx, I know, but don’t know what.
subpath is still not supported see Allow to deploy sao on subpath (#9239) · Issues · Tryton / Tryton · GitLab
Try adding:
proxy_set_header Origin ""; under the location block
I would not advise for such behavior because it will disable CORS protection.