Currently I am using a pi 3 model B+ as a mopidy server. I set this up at home and I was able to access the pi with the hostname from a browser (e.g. going to http://hostname.local/ in a browser). I am now back at uni and for some reason when I try the same http://hostname.local/, I get a message saying that the IP address cannot be found. Since I am at uni I am very restricted with what I can do. Many solutions involve setting up a static IP, which I cannot do since I cannot access the router config.
I am using avahi-daemon for the mDNS service.
As a side note, I can still access the pi by navigating to http://X.X.X.X/ (where X.X.X.X is the pi's IP). However this can be annoying since I need to connect with VNC (Since I have enabled cloud access) to find what the pi's IP is.
Things I have tried:
send host-name = gethostname();to
send host-name = "hostname.local.net"in dhclient.conf
nameserver X.X.X.Xin /etc/resolv.conf to
nameserver 188.8.131.52. However, on every reboot this value is removed and replaced by 3 separate nameserver values. This file also includes
domain [DOMAIN].ac.ukat the top. I'm not sure how relevant that is.
Other things that may be worth noting:
- I am not using Ethernet, I am using a WiFi connection. The WiFi network uses WPA2-Enterprise AES, with PEAP authentication (EAP-MSCHAP v2). The password for the network is not stored in plaintext in wpa_supplicant.conf, but is stored as a hashed value.
This question has been asked a lot but I have decided to ask specifically about my case since I cannot find solutions that work in my circumstances. I am not sure whether I just need to update a value somewhere since I have moved to a different network or not.
Any help is greatly appreciated.
It may go without saying but on the Pi that I am trying to configure, I am able to run the command
ping pihostname and
ping pihostname.local successfully, and the correct IP is pinged.