I was trying to find out the difference between a socket as a unix file and a socket that is a ip and port.

If I switch something like uwsgi to use a file instead of a port and ip, how do I then access uwsgi as a URL in my browser, since no port is now specified for my flask application.

3 Answers 3


Since this is the first result on Google for how to bind a flask UWSGI app to a unix socket, here is the answer to the question in the title.

From flask:



FLASK_APP=app.py flask run --host=unix:///tmp/app.sock

If using gunicorn:

gunicorn -w 4 package:app --bind unix:/tmp/app.sock

You can run uwsgi to listen to a TCP/IP port, for example uwsgi --http :80 , if you change it to listen to a Unix socket (for ex: uwsgi --socket :8000 ) then as you said, this is local only, no web service (TCP/IP) is exposed to the Internet and you have to put a web server like nginx in front of uwsgi as 'proxy' that can get the http requests from the outside world (see https://gist.github.com/evildmp/3094281 for a django example instead of Flask)

  • 3
    This doesn't actually answer the question of using a Unix socket.
    – larsks
    Oct 29, 2016 at 15:04
  • @larsks It does answer the question. It specifies exactly what you need (nginx or similar) in the middle to access it from a browser. Jun 17, 2021 at 5:22
  • 1
    It does not provide any example of using a unix socket. The examples in this answer show how to use network sockets. A unix socket is an entry in the filesystem, not a network port.
    – larsks
    Jun 17, 2021 at 12:33

Browsers don't support making requests to Unix sockets. Here's a feature request that was opened with Chromium, but they responded that they would not be adding support for that use case.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .