[unable to access gui, have to hard reboot the system]

FYI, the errors on libvirt have been sorted (i was moving the vmdk file to a faster drive). however, this problem spans several months and i only just started using vm's

[unable to access gui, have to hard reboot the system]

hi everybody. i'm having this issue more and more often now where i can't get to the GUI and can't even reboot via ssh (just hangs) i have to physically reach for the tower and reboot. this sytem is headless and that complicates things a bit further. can someone please help me look at my diagnostic file? thanks in advance.

unraid-tower-diagnostics-20230626-2318.zip

[[support] rix's Docker Repository]

On 3/17/2020 at 2:35 AM, zachrybaker said:

@rix I took a look at the docker file.  I think the answer to my question 1 above is the last line of that file tells docker to expose 53, so thats why Unraid shows it exposed.   I assume this is not going to get in the way, but also not breaking it technically, if I am set up for port 54? I'm kinda raw on this.

 

2. Why doesn't path resolution work?

Hi.. sorry i don't have an answer for you, but have you figured this out ? i am also having trouble w/ getting this docker to work. thnaks