+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: domain configuration (/showthread.php?tid=6000)
domain configuration - phorize - 12-08-2023
I messed up my in place upgrade from 8.3.6 to 8.3.7 so started again with a fresh flashed image. I've noticed that I can no longer access my pi using hostname.domain. I don't recall how the domain was configured in previous versions the hostname option in the system section won't accept values with a .domain in the them.
EDIT: i changed the hostname and added the local domain using hostnamectl set-hostname. I seem to remember that the hostname configuration could be done from the system menu in previous releases.
Trouble now is that the when I try and change other settings on the system section they can't be applied because the host.domain format isn't allowed in the hostname section.
RE: domain configuration - Tim Curtis - 12-08-2023
You can only specify the hostname in moOde either via the Raspberry Pi Imager or via System Config after the image has been prepped and boots.
A .domain suffix can't be entered in System Config or in the Imager. The domain .local is a builtin domain in OS's that causes an mDNS query to be issued for the host.
Changing the hostname outside of moOde will prolly result in a non-functional system.
Your best bet is to start with a fresh image, prep SSH, userid and password with the Imager and after booting the system try http://moode, moode.local or IP_adddress.
RE: domain configuration - phorize - 12-09-2023
(12-08-2023, 10:38 PM)Tim Curtis Wrote: You can only specify the hostname in moOde either via the Raspberry Pi Imager or via System Config after the image has been prepped and boots.
A .domain suffix can't be entered in System Config or in the Imager. The domain .local is a builtin domain in OS's that causes an mDNS query to be issued for the host.
Changing the hostname outside of moOde will prolly result in a non-functional system.
Your best bet is to start with a fresh image, prep SSH, userid and password with the Imager and after booting the system try http://moode, moode.local or IP_adddress.
Thanks. all fixed. I noticed that I hadn't turned ssh on in the imager. Wondering if that upset things. Anyway, all fine now. Thanks for the amazing work on this; the qobuz support is especially appreciated.