Hi All
With newest Docker Image 2026.2.0-ubuntu-24.04 im unable to login.
The File _framework/blazor.server.js is not available anymore which results in a JS Crash:
Result: Black Website after Login.
Looks like the Image has never been tested for me 😕
Best Regards
Andreas
0e34b57e-e86a-47c2-9817-2a13f6c67ae8.png
I see the same on my standalone test instance (also 2026.2.0-ubuntu-24.04)
On apps not requiring auth i see this error.
Images do not load. Including the Login page logo.
161f45fb-1f6d-4546-b2ee-83f3650dd951.png
cbcce70c-7977-4295-8001-cb82febfa33e.png
@Andreas @Dynamic66 We're tracking this one. We had an issue with publishing on Unix systems and this will be resolved in 2026.2.1.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
@Adam DriscollIs there an ETA? No pressure, I'm patient.
@Dynamic66 Next week. We have a couple other issues I would like to try to nail down so don't know the exact day but I don't want this one to linger.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
@Dynamic66 Next week. We have a couple other issues I would like to try to nail down so don't know the exact day but I don't want this one to linger.
@Adam Driscoll
Appreciated!
Feel free to reach out if you need someone to beta test it 👍
Heya, i have the same issue on standalone.
@Marco When you say stand alone, are you not using a docker container but are using Linux?
Adam Driscoll
PowerShell Expert and Developer at Devolutions
@Marco When you say stand alone, are you not using a docker container but are using Linux?
@Adam Driscoll
“I’m using it on a VM with Ubuntu LTS. It’s only my private test environment, so it’s not of great relevance. I just wanted to add my comment to the discussion.”
@Dynamic66 Next week. We have a couple other issues I would like to try to nail down so don't know the exact day but I don't want this one to linger.
@Adam Driscoll
Hey Adam,
Eighteen days ago you said the fix would be out "next week." I completely get wanting to nail down the other issues first; better than shipping something broken. But I have to ask: how exactly are we defining "next week" here?
You said yourself you didn't want this one to linger, and right now it kind of is. Back when you were doing weekly updates, this would've been out the door already, so I know it's well within your reach. Would a small quickfix for just this one issue be too much to ask while you finish off the rest?
Thanks for all the work you put into this, just really hoping to see this one move soon.
Cheers
The 2026.2.0 docker tags really should be unpublished. They are unusable and anyone upgrading to latest will end up with a broken environment.
This issue has been resolved and will be included in 2026.2.1 and is scheduled for release this Friday. I appreciate your patience.
Adam Driscoll
PowerShell Expert and Developer at Devolutions