[pkg-uWSGI-devel] Bug#752783: I think I found the solution / workaround

Attila-Mihály Balázs dify.ltd at gmail.com
Thu Oct 1 17:38:48 UTC 2015

For the first problem (unix sockets not working with mod_proxy_uwsgi), 
the following patch solved the problem for me: 

Until that lands, I found the following work-around:
- change "socket" to "http-socket" in uwsgi.ini (so that uwsgi speaks 
http instead of the uwsgi protocol)
- use "vanilla" mod_proxy_http over unix domain sockets:

ProxyPass "/foo" "unix:/var/run/uwsgi/foo.socket|http://uwsgi-uds-foo/"

- the problem with the port not being parsed when TCP was being used was 
fully PEBCAK - I had a different virtualhost config getting activated 
than the one I believed was getting activated. mod_proxy_uwsgi properly 
parses and uses the port for TCP connections.


PS. Apparently, if you have multiple instances of uwsgi you want to 
connect to, you need to specify different names for them (ie. 
"http://uwsgi-uds-foo/", "http://uwsgi-uds-bar/", etc), having just 
different paths to the sockets will not work.

More information about the pkg-uWSGI-devel mailing list