Do not change host name before installing about iotstack HOT 9 CLOSED

Hi Paul, thanks again for your contributions.

I just tested changing the name. I had burned a new sd card for my 3B last week and changed the name back then.
I ran the install from the menu and docker install without any issues.

I know i used raspi-config to do the change. how did you change the name?

from iotstack.

I also used raspi-config. I will need to run a new image again to replicate and will post the results.

from iotstack.

Hi Paul, have you managed to replicate this?
Today i burned new Lite image, changed the name and installed docker without issues.

from iotstack.

@Paulf007 you said you changed host name via raspi-config so the following should not be an issue in that case: my experience is that changing host name with the hostname command on Raspbian does not work correctly, but changing it with raspi-config does. Not sure if required but I always reboot after changing the host name.

from iotstack.

I’ve done several “from scratch” builds. I wanted to be able to run the RPi4 from a USB-3 SSD and was trying to figure out an optimal path so that I could document it and never have to think about it again. Each time I renamed the Pi using raspi-config, followed by a reboot. The “sudo reboot” immediately after the name change would always complain about not being able to find something to do with the default name but that was the only hassle. After that everything Including installing IOTStack just worked.

from iotstack.

I did a build of a zero w yesterday, I changes the name and on the sudo reboot (all of this was done over ssh because i was to lazy to go find my mini hdmi cable) it also gave an error regarding not being able to resolve the name. However when it rebooted it had the new name and it went on with out a problem. Do you think its a problem? Do you not think its the ssh channel that gets a name conflict?

from iotstack.

My instinct is that it’s probably nothing other than what it seems - logged in under one hostname, the rug pulled from under it by the rename, grizzle at the logout forced by the shutdown. My only lingering doubt is why the PiHole URL without the /admin suffix doesn’t work and is also grizzling about names. I don’t see why they should be related - none of the Docker stuff is being installed until long after the rename (in my case, anyway). That really only leaves two possibilities: a hard-coded reference somewhere to the default name (which seems unlikely), or something wrong with the supplied PiHole install script.

Sorry that this case is now getting tangled up with #60. I was trying to reassure Paulf007 that renaming via raspi-config did work, at least for me.

from iotstack.

@Paraphraser i just did a stupid test on pihole now, i changed its port 80## to port 80. now when i navigate to my IP is shows the correct page asking to redirect to the admin page. This is on my Pi running from my project

i was looking through some issues on piholes github page and I saw some references to reverse proxies not redirecting when you change the port away from 80.

from iotstack.

this doesnt seem to be an issue and pihole conversation merged with #72

from iotstack.