Hello, i’m new here. I surely jumped the presentetion rule 
I freshly intalled zimaos v1.4.4-1, and oly use it (for now) as container for pi.hole. It stopped giving me acces after I visited a Tv streaming web page (official, frre to view streming webpage of a Sky tv associate), ora at least I became aware of the problem after that ( I wanted to check what pi.hole blocked in thatg page). It wa unaccessible. I was considering restarting the minipc wioth zimaos on it, but I first cheched the router (Iliadbox 5) to see if it was still on the conencted and known devices. I t was not. Bu restarti my main pc(?) gave me back acces to the zimaos machine without restartingb the zimaos machine. Probabably a coincidence but this is what happened. My hypotesies would be, energy saving settings on the ziamaos machine(?) network adapter woken up by restarting windows(?). I really did not do anything othe than cheching the router and then restarting my pc minutes later. Hope the it can help. Mushi
Apps like pi.hole and Adguard will affect your network connectivity. Try to shut them down and give ZimaOS a static IP address. Look forward to your feedback.
Thank you for the quick answer 
My ZimaOs machine has already a static ip, out of DHCP range. I use it as dns server for my network, via Pi-hole. So I rarely interact directly with the minipc if not for checking on it via browser. I discovered its inaccessibility by chance checking on it and entering the community I saw posts about similar issues and wanted to add my experience. I will add later my hardware configuration for better understanding
I have similar behaviour on Zimaboard2, yesterday was fine and everything worked, today no access to smb/dashboard… I don’t have a monitor in a rack, but the board was very hot, so I assume something was stuck… after reboot, everything is working fine. If it happens again, I will bring the monitor to check the activity…