UI in Chrome browser is not displayed correctly

[Terion]

Hello everyone

I have just registered on your forum and would like to ask if anyone can help me with my problem.

I have installed the latest version of WebDOM (as of January 30, 2026) on my Windows 11 computer (Docker, WSL 2 with Ubuntu 24 LTS).

I can start the application without any errors up to the console prompt, which means I can now access localhost:8000 via my browser.

In the Chrome browser (current version), I see an almost entirely blue screen. I can still see the black borders around the login credentials fields, the white logo in the top left corner, and the falling colored confetti. The page responds correctly (e.g., when clicking on the button position with the mouse), but the colors are displayed incorrectly, rendering it unusable.

In developer mode, I see error messages stating that some files cannot be accessed.

Does anyone know the possible cause of my problem?

I was able to try the following with the help of AI and thus rule it out:

- Translation is disabled in the browser

- Hardware graphics acceleration is disabled in the browser

- Browser cache cleared

- WSL has 16GB RAM, 16GB swap memory, and 1TB HD memory

- WebODM Docker image terminated/restarted several times

- Firewall open for incoming requests on port 8000

- Accessed specific WSL IP instead of localhost

- Permissions for /static /media shared in WSL

- Previous version of WebODM from 2023 installed/tested → same problem

I would be very grateful if someone could give me a tip.

Either way, thank you very much and best regards,

Terion

[pierotofy]

This is probably due to incompatible python venv requirements · Issue #1831 · OpenDroneMap/WebODM · GitHub which has been fixed.

./webodm.sh update && ./webodm.sh restart

[Terion]

Hello pierotofy

Thank you very much for your prompt and valuable response.

It would be great, of course, if I could solve this problem with ‘just’ an update (unfortunately, I can’t test it until the weekend).

The following makes me a little suspicious:

I tried downgrading WebODM to previous versions (2.9.5 and then even to a version from 2023). The problem occurred in both cases.

Either way, I will gladly test your advice and am very grateful for your suggestion.

Thank you again and best regards

[pierotofy]

If you just installed it and you don’t have any data to lose, I recommend resetting docker to factory default, which will remove all previous data and volumes, then update/restart WebODM which will give you a fresh install.

[Terion]

Great, thanks a lot.

I’ll try that.