(Not your fault but you could still improve docs) Nobody mentioned that some KVM default to raw and you need to define it as qcow2 (for example in UNRAID, edit the VM xml).
It started and I logged in console with default root password, where it forced me to change password. I assume this didn’t touch admin’s password, only root (again make docs “stupid proof” by mentioning it).
I run nmtui to edit the network configuration (you should also say in the docs that probably “Wired Connection 1” is the adapter you need to edit). Also since it is a server maybe first login should force nmtui, as getting DHCP address is probably not best practice.
I rebooted the VM (also not clear what to do to apply network changes).
This time the login prompt mentioned I should use node.ns8.test:9090 (???)… Hardly. Would probably only work if clients used NS8 test as gateway and/or DNS? Else it doesn’t work. Of course, it also lists the ip: https://[ip I defined in nmtui]:9090.
So I connect to that using web. I see Rocky Linux (and not “NethServer8”… shouldn’t it say that?) login prompt… Well NO GO. It doesn’t work with user root or admin and either default (Nethesis,1234) or the forced changed root password. It says “Wrong user name or password”. Tried several times even with copy/paste.
http(s)://[ip I defined in nmtui]/cluster-admin does nothing (fails).
Thank you for your reply mrmarkuz.
The main problem then, is my last bullet.
cluster-admin never worked then (accessing from IP) - from the premade image.
It is possible that something stops the “first run” and never resumes?
Maybe there should be a check script to see if everything went fine?
Why would that make a difference, Dan, I am really interested.
It’s been years since I last heard it mattered.
All web servers I know are smart enough to understand if the URL ends in a file or a folder.
So I started from new image.
I edited network settings and enabled them without rebooting.
cluster-admin (with or without trailing slash) works this time.
I rebooted, it still works.
Only difference from first time is that in the first time the image didn’t boot 3-4 times because it was not set as qcow2 (shouldn’t be related to the issue) and that last time I edited the network settings and then rebooted (which DID make the network settings change). I never saw cluster-admin.
It seems weird that this little difference could affect the whole server.
Also I would DEFINITELY expect pre-built images to force me edit the IP or inform me of current IP at least (as I could have arranged things from DHCP side) when they first boot. It is not clear in the docs (yes it is “more or less mentioned” with “if you have network issues” etc. - but definitely needs to be cleaner) what you need to do.
Thanks for all the help.
PS. Rocky Linux cockpit, still doesn’t allow login of root by default. I find it a bit weird, but I guess that is Rocky Linux issue or policy.