Nginx proxypass killing httpfrontend

So iv gotten quite a few extensions working how i want them including a few front end web gui’s but i would like to setup nginx to redirect port 80 to one front end and port 85 and 87(picked at random) to redirect to other front end extensions.

Right now iv got no issue using mopidy’s http server directly ip-address:6680/extension-name/ works great.

my goal is to eliminate the need for port 6680 and the directory traversal.
i have used iptables to point port 80 at 6680 so i can get that part but the does not help me with the other extensions.
i know you can set a default front end in the http config but that’s not the whole goal.

End game here wqould be
-"ip-address:6680’ would take me to the regular mopidy page where you select a frontend
-“ip-address” defaults to port 80 which goes to the extension 1 front end
-“ip-address:85” goes to extension 2
-“ip-address:87” goes to extension 3

Here is my mopidy config:
enabled = true
hostname =
port = 6680
zeroconf = Mopidy HTTP server on $hostname
allowed_origins =
csrf_protection = true
#default_app = mopidy

output = alsasink

username = *****************
password = *******************
client_id = ******************
client_secret = **********************

auth_token = **************************

enabled = true
musicbox = false
websocket_host =
websocket_port =
on_track_click = PLAY_NEXT

and here is my nginx config:
server {
listen 80;

location / {


server {
listen 85;

location / {


server {
listen 87;

location / {


these configs get me to the extensions but then there is no connection to mopidy after. like when i use the musicbox client it just says “trying to reach to mopidy at Please wait” and the other extensions are completely unresponsive they load the web page but you cant interact with anything.

You need something in those nginx config to handle the websocket that’s used for Mopidy’s RPC. I think there might be example nginx configs on here somewhereiif you search but I’m not familiar enough with it to give specifics here.

Ok. at least i have an identified problem. Unfortunately this is a little above my head. Is the a specific type of RPC web socket that mopidy uses that i can research nginx compatibility and configs for?

No, just a regular websocket. if you search on here you’ll find an example config at [SOLVED] Websocket randomly reconnects when running Mopidy through a reverse SSH tunnel and also at Mopidy Raspberry Pi and Nginx and probably others if you look.