Have you only tried to access through the domain? Have you tried accessing via IP?
Did you update your dns record to point to OMV?
Hello, thank you very much for the quick feedback.
Yes, I usually always use the IP address and not the host name in the browser.
How should I enter this https://openmediavault:80 or https://openmediavault.workgroup:80?
Since I couldn't shut down the device via ssh. I unplugged it from the power. Now he doesn't get an IP address assigned because he no longer appears on the network.
Have I completely killed the system?
Have you only tried to access through the domain? Have you tried accessing via IP?
Did you update your dns record to point to OMV?
I think I don't have a DNS server running. 
How should I enter this https://openmediavault:80 or https://openmediavault.workgroup:80?
If you access port 80 it is not https, it should be http, and it should not be necessary to add the port. Just http://openmediavault. All this assuming that the OMV host is "openmediavault" and that your client is capable of recognizing domain names. Windows usually crashes randomly on this. The IP address never fails.
Since I couldn't shut down the device via ssh. I unplugged it from the power. Now he doesn't get an IP address assigned because he no longer appears on the network.
Have I completely killed the system?
Look up the server's IP address on the router.
Can you hook a monitor to the pi? If so you can use the cli (terminal). Then use omv-firstaid to set a static ip.
You must have a dns or you couldn't get to the internet. It may be your router. If so you may be able to set a static ip reservation for the pi on that. It depends on your router how to do it. Then you probably can use the name to connect to omv.
The same thing happens to me. I have a Raspberry Pi 4 with a clean installation of Openmediavault 7 on a 128Gb SSD. By changing the IP to static or setting the domain to local, when it restarts you can no longer access the Raspberry in any way. It is not visible on the network even if I turn it off and on again. I do not know what is the problem.
You should be able to access with http://ip of OMV. Your browser may say it is insecure because it's http and not https.
Secondly
It is best to set your Router with reserve IP's, I reserve the first 192.x.x.1 - 192.x.x.10 for static machines, 192.x.x.1 being my gateway, and the next 3 are Satellites, up to 10 are my NAS's, server, smarthome hub, printer. And set static IP's on them so they never change.
On the router the Raspberry appears offline
If you hook an hdmi to the pi does it give you a console?
I can't test it right now because I don't have a microHDMI on hand
Hey,
may I jump in here?
Having exactly the same issue on a RPI4.
It appears that this is happening as soon as anything is touched regarding the network settings.
For sure it is happening when changing the domain, setting a fixed ip or disabeling IPV6.
Console shows systemd-networkd-wait-online runs into an error/timeout.
I could not find any specific errors in journal or dmesg.
Anything else I could check?
Thanks a lot.
One other thing I forgot to mention that I have run into changing PCI slot on NIC.
Even though it cam back up with same device name and everything looked the same, It would not connect for updates till I input the DNS numbers for the network device in OMV and restarted.
Even though it showed on line and I didn't have to do that at install.
I have the same problem. Trying to change the Pi to a fixed IP address within OMV fails and bricks the ethernet interface. I even tried setting up wlan0 interface as a backup and found that even trying to activate wifi causes an error in OMV and won't allow the interface to be added or the config changes to be saved. This never used to happen in the older version I had setup on a Pi3. I tried nano /etc/network/interfaces but OMV is superseding that. I can login to console evetually after it times out on a reboot but I am not sure how to fix this.
Trying to change the Pi to a fixed IP address within OMV fails and bricks the ethernet interface. I even tried setting up wlan0 interface as a backup and found that even trying to activate wifi causes an error in OMV and won't allow the interface to be added or the config changes to be saved. This never used to happen in the older version I had setup on a Pi3.
Have you tried this -> installation process?
There's a preinstall script that takes care of the networking issue.
Sorry I don't do PI, I would have thought it would be the same on any hardware.
I know occasionally you have to Ctrl-Shift-R in browser for salt to reset and some browsers will balk at none https:
I'd suggest PI forums.
Had the same thing happen to me as OP.
This fixed the issue for me
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
