Just getting a blank screen when trying to load umbraco 15

For the past year, I’ve been running Umbraco 15 locally on my M2 Mac using Parallels with a Windows 11 VM. Since I couldn’t figure out how to run a database within Windows, I’ve been hosting it on my Mac using Docker and connecting via IP. I also had Umbraco set up directly on my Mac, but that setup has been broken for a while. I prefer using Visual Studio, so I had no problem sticking with the Windows VM.

Now to the issue: starting last week, Umbraco began showing a blank screen when running. It builds fine, but the UI is completely blank. I took this as an opportunity to fix the Mac setup, which now builds again—but it has the same blank screen issue.

Since both the Mac and Windows environments produce the same problem, I suspect the database is the culprit, as it’s the common link between the two (or at least I think it is). I tried rolling Docker back to an earlier version, deleted and reinstalled the azuresqledge container/image/volume, and re-ran the database setup script multiple times.

Despite all this, the issue persists. Umbraco logs show no errors, the browser console is clean, and inspecting the page reveals it’s nearly empty.

Has anyone seen this before? Do you have any other ideas how I can troubleshoot it? Is there something within our servers or company that it pings to that may have messed up permissions?

I should add, no one else in the office is getting this, just me.

Any console / javascript errors?

1 Like

Does the user account you’re using have a role assigned with start nodes and view permissions for the backoffice?

Though, I think if this was the case you would still at least see the top banner with the Umbraco logo but nothing else :thinking:

1 Like

@Ambertvu and @nobledm
Hello,

Thank you both so much for getting back to me. My trouble for troubleshooting was when going to an old branch to test I forgot I had merged that branch with main. A coworker got the same issue when he blew away his DB to start fresh and run uSync. So I knew it wasn’t just me. Anyway, he had an even older branch and it worked fine so we started testing and found out when it was when we started adding compression.

We comment out app.MapStaticAssets(); in our program to turn off compression for the css and js and then the setup works. Then we uncomment it and it works like normal after the setup script runs. We are debugging from there but that’s an easier place now that we know what causes it.

Thank you both for your suggestions!

1 Like