Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't connect

See original GitHub issue

Hi,

I installed mopify on Arch running on a Raspberry PI. I can see it is running because using netstat I see this line

tcp        0      0 127.0.0.1:6680          0.0.0.0:*               LISTEN

but I cannot access it through the browser:

http://192.168.1.81:6680/mopify/ (connection refused)

Is there anything I need to change in the mopidy configurations?

Thanks

Issue Analytics

State:
Created 7 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

kingostickscommented, Nov 20, 2016

Change the hostname config value to either 0.0.0.0 or :: as described at https://docs.mopidy.com/en/latest/ext/http/#confval-http/hostname

0reactions

dirkgroenencommented, Nov 20, 2016

You can use pulsaudio and alsamixer, that’s not an issue. Alsamixer not wanting to start (after installing alsa-utils) could suggest you have no sound driver/detected sound card. Check your aplay -l output and see if any cards are recognized.

I’ll close this issue since this is, as @kingosticks said, not related to Mopify. I would suggest to do some searching on Google and check the Arch documentation. They’ve a solid documentation that should you get out of these kind of issues.