I'm on a trial license of unraid 7.3.1, it's my first time using it and I'm a newb with server and network stuff. I followed some youtube videos and was able to get my server running, I have a cache pool running and next I wanted to install some apps. I clicked on the initial install button from the unraid apps tab. Then I got the error message "Browser failed to communicate with unraid server". It offers to try to fix by reloading the page - that does not work. I edited the DNS servers to what was in the unraid docs. Tried a reboot of my server. The PHP Settings log is empty. Any suggestions?

Do you have an attached monitor and keyboard?

Hello,

Sorry for the delay in replying. Yes, I do have an attached keyboard and monitor, but I am primarily working through the web GUI. Since I posted this the other day I have updated BIOS and uninstalled and reinstalled the community apps through the web GUI. Still having the same result. I've attached a diagnostic zip.

nas1-diagnostics-20260609-2058.zip

Jun 9 20:52:57 NAS1 kernel: __vm_enough_memory: pid: 5571, comm: docker, bytes: 549760008192 not enough memory for the allocation

A Docker container just tried to allocate 549,760,008,192 bytes of memory. That is 549 GB of RAM.

Try recreating the Docker image in case something is corrupted, then restore your assp one by one

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file

Then:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

If issues continue, it could also be bad RAM.

4 hours ago, JorgeB said:

549760008192

In binary this is

1000000000000000010000000000000000000000

If you flip that most significant bit it is a more reasonable

4194304 in decimal

= 4 x 1024 x 1024

= 4 MB

4 hours ago, JorgeB said:

it could also be bad RAM.

Do memtest before anything else.

Thank you both. I ran the memtest and immediately had thousands of failures coming in. I bought the RAM brand new for this build. I'll try to reseat it and rerun the test. If that doesn't work, I'll try replacing it.

Reseated the RAM and still had failures instantly. Is it common for brand new RAM to come in dead? G.Skill Flare X5 DDR5-6000 CL36 from NewEgg

Test each stick one at a time in each slot

I replaced the RAM and it solved the problem. Thanks for the help!