# Web browser on Android not connecting to to Mopidy on PI

**URL:** <https://discourse.mopidy.com/t/web-browser-on-android-not-connecting-to-to-mopidy-on-pi/3626>\
**Category:** Misc\
**Created:** [December 14, 2019, 3:15pm UTC](https://discourse.mopidy.com/t/web-browser-on-android-not-connecting-to-to-mopidy-on-pi/3626 "2019-12-14T15:15:31Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Steve\_Lambert](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/steve_lambert/32/1149_2.png) [@Steve\_Lambert](https://discourse.mopidy.com/u/Steve_Lambert)\
**Post date:** [December 14, 2019, 5:11pm UTC](https://discourse.mopidy.com/t/web-browser-on-android-not-connecting-to-to-mopidy-on-pi/3626/2 "2019-12-14T17:11:40Z")

</div>

Some time ago this used to be because Android didn’t recognise the name.local so you had to find the mopidy instance by using the ip address (192.168.0.??) followed by 6680 etc.  
More and fuller explanation [here](https://discourse.mopidy.com/t/cant-access-web-interface-from-mobile-phone/730)  
Whether this still is the case I’m not sure.

---

_[View the full topic](https://discourse.mopidy.com/t/web-browser-on-android-not-connecting-to-to-mopidy-on-pi/3626)._