[BUG] Dashy 3.0.0 not loading despite complete build

[allesauseinerhand]

Environment

Self-Hosted (Docker)

System

Docker 26.0.0 (Portainer 2.19.4)

Version

3.0.0

Describe the problem

Thank you for the new and promising update to 3.0.0. But it seems, I have some trouble to get it to work:

1. I changed the port from 80 to 8080 and the volume from /app/public to /app/user-data
2. I pulled the new image and started the container
3. The state of the container is healthy
4. The logs seem to be fine too ("Config file is valid, no issues found"; "Using Dashy V-3.0.0. Update Check Complete"; "Build complete. The dist directory is ready to be deployed."). The only thing, that I'm not sure, if this is OK: the last line in the logs is "Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html"
5. When I try to open the service in the browser, it shows "Loading" for some seconds and then presents me with a message "It looks like something's gone wrong... This is likely caused by the app source not being found at the current domain. If you need additional support, check the browser console then raise a ticket"

Additional info

I attached the screenshot with the error message, the full logs and my docker compose instructions.

_dashy_logs.txt
dashy_docker_compose.txt

Please tick the boxes

• You have explained the issue clearly, and included all relevant info
• You are using a supported version of Dashy
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[CrazyWolf13]

Can you paste the browser console output?

How long have you waited after the error message appeared, sometimes refreshing the page also resolved the issue.

[allesauseinerhand]

Hi Tobias, thanks for looking at the issue. Here is the browser console output just logged after entering the url. It doesn't change when the error message appears. So probably no client-side problem.

[ContentMain]
ContentMain.js:5 [ContentService] document.readyState: loading
ContentMain.js:5 [ContentService.SetContentInitData] target: { TabId: 662559308, FrameId: 0}

[allesauseinerhand]

How long have you waited after the error message appeared, sometimes refreshing the page also resolved the issue.

I have waited several minutes, I did refresh (F5) and I tried in Chrome (Guest Mode) and MS Edge

[rodalpho]

I changed my config to look like yours (with my paths) and had no issues with the 3.0 changes, loaded fine. I did need to map /app/public/ inside the container to get the icons to show up properly; possibly they would work inside user-data/ also. User-data/ needs the conf.yml file, and public/ needs fonts/, img/, item-icons/, etc. The docs on the 3.0 upgrade aren't... great so this took a couple mins to figure out properly.

My volumes line:

    volumes:
     - /opt/dashy/user-data/:/app/user-data/
     - /opt/dashy/public/:/app/public/

On a side note, man, dashy takes a crazy long time to start up. My relatively simple dashboard takes 55 seconds! I'm not running a rPi4 or anything underpowered either, it's a 7500T mini-desktop with tons of RAM and free CPU.

2024-04-20T16:58:21.719069075Z  DONE  Compiled successfully in 54820ms4:58:21 PM	 

[allesauseinerhand]

@rodalpho Thank you for your time to add a solution, that worked for you. Sadly it doesn't work for me. I did now map the two volumes, but it didn't change anything with my problem.

volumes:
 - /dockerdata-fast/config/homepage/dashy_public_dir:/app/user-data
 - /dockerdata-fast/config/homepage/dashy_public_dir:/app/public

By the way, this is the content of my dashy_public_dir folder:

A question about your logs: is the last line of your log also "Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html" or is it something else?

[Lissy93]

Hey @allesauseinerhand
Sorry you're having issues. It looks like your config isn't being passed to Docker correctly - If you visit [dashy-url]/conf.yml what you you see?
Maybe the issue is because initially the paths were wrong, and so the initial (and only) build happened without a config. In which case, starting fresh should resolve it.

[Lissy93]

Thanks @rodalpho

. I did need to map /app/public/ inside the container to get the icons to show up properly; possibly they would work inside user-data/ also. User-data/ needs the conf.yml file, and public/ needs fonts/, img/, item-icons/, etc.

Both /public and /user-data basically resolve to the same place. So you shouldn't need to pass both in, just put all your customized assets into user-data

---

The docs on the 3.0 upgrade aren't... great so this took a couple mins to figure out properly

Sorry about that (I'm not great at writing docs!), if you have suggestions about how I can make this clearer, I will update them :)

[rodalpho]

@allesauseinerhand Yes my logs end with that line.

@Lissy93 No problem, not intending to criticize! I would note the expected file and directory structure for /app/user-data/, that's what had me stalled for a minute. IE, "It should contain conf.yml as well as the fonts, img, item-icons, etc directories".