thatguy5555

I am having issues on several of my VMs that I use to access unraid. This problem is not encountered on other VMs on the same vLAN, so it seems very strange. I have tried disabling my Windows Defender firewall and it still gets this error. How to recreate problem: I successfully log into the unraid web interface. I am using https to connect to unraid. I then go to docker and attempt to open the webui for a docker container (example: binhex-krusader) I get an error "ERR_CONNECTION_REFUSED". I have tried both Brave browser and Edge browser and get the same error. This only occurs for dockers that are in "bridge" network mode. It does not occur for custom network modes. Those work fine. Any thoughts? I'd love to not have to abandon these VMs just to access docker containers as this is occuring on my daily driver VM.

Solved: I realized that I was utilizing my Intel Graphics card for a VM. The screen would kick out after the VM initiated at startup and took the graphics card away from unRAID. Solved the problem by not starting the VM.

I am trying to get direct access on my unRAID machine working in case i have a network or other catastrophic error in the future. This is my personal home installation, and having access to the unRAID GUI gives me some confidence as I work to convert from my UniFI USG to pfSense, currently running in an unRAID VM. My issue is that the monitor hooked up to my unRAID server (Gigabyte B360M DS3H motherboard utilizing onboard Intel Graphics) will display properly until the boot login screen for unRAID. The monitor will go from displaying properly to briefly displaying many colors like a connection error, to showing nothing and going into standby mode. The entire time, the server is up and running and accessible over the network. I have tried tweaking some settings in the motherboard and adding the "nomodeset" boot command. Can someone please take a look at my motherboard options and suggest anything else I can try? I've attached screen shots of the motherboard bios screens. Things I've tried: -Changing "VGA Support" - "EFI Driver" with and without "nomodeset" --> "Automatic" with and without "nomodeset"