mirror of
https://github.com/Corsinvest/cv4pve-admin.git
synced 2026-04-25 12:55:57 +03:00
[GH-ISSUE #172] [Bug]Borked Layout of Web-UI in 2.0.0-rc[X]: #61
Labels
No labels
bug
bug
enhancement
feedback
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cv4pve-admin#61
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tastelessbrain on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-admin/issues/172
Edition
Community Edition (CE)
Version
2.0.0-rc2
Deployment Type
Docker
Bug Description
When i Use any 2.0.0-rc image the Layout and or Scaling of the webui is completly gone.
Steps to Reproduce
Expected Behavior
I expected something like this:
https://corsinvest.github.io/cv4pve-admin/images/login.png
Actual Behavior
I get this:

Relevant Logs
Environment Details
No response
Additional Context
No response
@franklupo commented on GitHub (Feb 18, 2026):
Hi @tastelessbrain,
Looking at your logs, the broken layout is caused by the app failing to run database migrations and read settings at startup:
The PostgreSQL volume appears to be corrupted or in an inconsistent state, which prevents migrations from running and settings from being loaded — resulting in the broken UI layout.
To fix, try a clean restart:
If that doesn't help, remove the corrupted PostgreSQL volume and start fresh:
Also note: the
Connection refusederror onregistry.hub.docker.comjust means the container has no internet access — this does not affect the layout.Please let us know if this resolves the issue!
@franklupo commented on GitHub (Feb 18, 2026):
Hi @tastelessbrain,
Looking at your screenshots, it seems the broken layout is on the login page. Can you confirm:
Thanks!
@tastelessbrain commented on GitHub (Feb 18, 2026):
@franklupo as you can see on the second screenshot its also on the setupwizard after login.
Ill look into the tip from your 1st response.
Thx so far.
@franklupo commented on GitHub (Feb 18, 2026):
Thanks for the confirmation! The broken layout on both the login page and setup wizard looks like missing CSS/static files rather than a data issue. We're investigating this further.
@tastelessbrain commented on GitHub (Feb 18, 2026):
[EDIT: Format and added logs of postgres.]
So i spun the setup up at my home machine for testing using the same steps. But without any firewall in front. result is the same. Exept the refused connection i think.
The console output you asked for:
I also added the ls -lah output of my dircetorys as a txt file.
ls-lah.txt
Logs after compose down & up only (no change in behaviour):
Logs after docker compose down -v && docker compose up -d (also tried the ./adminctl but to no evail):
Logs after completly deleting the folders and starting new:
Postgres Logs:
ls-lah.txt
@tastelessbrain commented on GitHub (Feb 18, 2026):
Im so sorry for te format i will fix it as fast as possible
should be better now. Good night and thx in advance! :)
@franklupo commented on GitHub (Feb 19, 2026):
Thanks for the screenshot! The console warning about the font is not the cause.
To better diagnose the broken layout, could you open the browser DevTools (F12) → Network tab, reload the page, and share a screenshot of the Network tab? We want to see if any CSS or JS files are failing to load (red rows with 404 or other errors).
Thanks!
@tastelessbrain commented on GitHub (Feb 19, 2026):
@franklupo commented on GitHub (Feb 19, 2026):
Hi, thanks for reporting this!
We found the issue and we are working on the fix. It will be included in the next release.
@tastelessbrain commented on GitHub (Feb 19, 2026):
Perfect, thank you. I was just thinking the Layer 8 was particularly strong in me. :D
@franklupo commented on GitHub (Feb 19, 2026):
Fixed in v2.0.0-rc5. Please test and let us know if everything works correctly. Thank you!
@franklupo commented on GitHub (Feb 20, 2026):
news?
@tastelessbrain commented on GitHub (Feb 20, 2026):
Love you guys. Great Work. Seems to work at least in my home lab. Will Test Monday at work.
Will report back, but i think we can close this monday.
Last unrelated quick question:
Do i still need to allow SSH User & PW authentication or is API Key and or SSH Key enough in version 2.0.0?
Thanks for your work and wonderful Support. <3
@tastelessbrain commented on GitHub (Feb 23, 2026):
Also works at work now. Thank you! can be closed.