I installed Mopidy on Raspberry Pi. I want to control it by web clients, on the same wifi network. I enabled the http extension. If I change the hostname parameter in the [http] part in the mopidy.conf file, I’m able to reach the Raspberry Pi by http:// 192.168.0.200:6680.
But I would like to avoid the 6680 port ( lazyness ), so I installed nginx and configured it, like this link describes ( https://gist.github.com/BenMatheja/9230138 ).
When I try to reach the Raspberry pi over http:// 192.168.0.200, it gives me 502 bad gateway error, and in the nginxe error.log it says “Connection refused 111”.
Hello,
Has anyone here in the forum tried to redirect an mopidy extension to an auth/login page
via nginx? The idea behind is to accept public access for mopidy-party,
and restricted access for mopidy-mobile.
My current (working) nginx config to shorten the path for mopidy-party: