[BUG] Just upgraded and it never brings up the page.

[bonelifer]

[BUG] Just upgraded and it never brings up the page.

[DeltaTangoLima]

every sysadmin should know that, not to just blindly update stuff

No need for the passive aggression. A simple "did you notice the breaking changes in the latest major release" would suffice, without sounding condescending.

In return, I'm used to devs that announce significant breaking changes in a way that's difficult to miss. A meek little note at the top of the README doesn't really draw attention that well, does it?

Thanks for the tip.

[CrazyWolf13]

Hi @bonelifer @DeltaTangoLima

Dashy has got a major update from 2.x to 3.x.

I sincerely recommend to check out the release notes when updating, every sysadmin should know that, not to just blindly update stuff.

It has been documented here:

#1537
#1529
And with a note on the main readme:

Also take a look at the Docker Compose file, it was updated as well.

Version: "CURRENT" is also not really helpful, please don't write such things, as there is only a latest tag or a specific version.

[DeltaTangoLima]

Very similar issue - just upgraded Docker image and all I get is the default start page (screenshot) - not my configured page.

Docker logs state that config is valid, and I've confirmed my bound volume for conf.yml is indeed mapped correctly to /app/public/conf.yml inside the running container.

Rolling back to the previous image works fine.

[bonelifer]

I dont get that as it literally reports healthy in portainer. But my browser says it can't connect.

[bonelifer]

Firefox and Chromium both give the site can not be found message.

[bonelifer]

I had to roll back to 2.1.0/2.1.2, to get dashy to load(older one trying to get my current yml to load), but now it wont load my config.yml, have reset local and rebuild from the app. Just end up with defaut config. Would be nice to have local in browser import of the config.yml. I wish I could remember the cloud info for my last backup.

---
services:
    dashy:
        ports:
            - '4000:80'
        volumes:
            - ./data/config.yml:/app/user-data/conf.yml
            - ./data/item-icons:/app/public/item-icons
        container_name: dashy

    # Specify restart policy
        restart: unless-stopped

        image: 'lissy93/dashy:2.1.0'
        environment:
            - NODE_ENV=production
            - UID=1000
            - GID=1000

    # Configure healthchecks
        healthcheck:
            test: ['CMD', 'node', '/app/services/healthcheck']
            interval: 1m30s
            timeout: 10s
            retries: 3
            start_period: 40s

[CrazyWolf13]

Sorry for that tone, wasn't meant to sound like that at all. 🙂

In return, I'm used to devs that announce significant breaking changes in a way that's difficult to miss. A meek little note at the top of the README doesn't really draw attention that well, does it?

Yes that's completely correct, I'd also have announced it differently, but I'm not the owner.

As far as I know there should have been a note inside the dashy app itself in the log and on the UI, if dashy was updated without the path or port changes, but could also be broken, due to a direct update to 3.0.1. QA
I'll forward it to lissy.

As for you both, you are still on port 80 instead of port 8080.

[DeltaTangoLima]

Sorry for that tone, wasn't meant to sound like that at all. 🙂

All good mate. I've remapped my bind mount (and remapped to port 8080) and everything's working perfectly. Cheers!

[CrazyWolf13]

Awesome 😎

[CrazyWolf13]

@bonelifer Can you confirm this works for you aswell?

[Luksagon]

I have the same issue as bonelifer, with the same (or at least very similar) logs with the .js and .css files.

I have updated the port mapping and the mounting directory as described. Did not work.

I have now rolled back tot version 2.1.2 which is working without issues

[CrazyWolf13]

I have the same issue as bonelifer, with the same (or at least very similar) logs with the .js and .css files.

I have updated the port mapping and the mounting directory as described. Did not work.

I have now rolled back tot version 2.1.2 which is working without issues

Can you externally backup config and other possibly mounted things and then fully rebuild the container, re pulling the image etc. Without any mounts, then the default config should appear, then mount the config file and check again.

[Luksagon]

I have the same issue as bonelifer, with the same (or at least very similar) logs with the .js and .css files.
I have updated the port mapping and the mounting directory as described. Did not work.
I have now rolled back tot version 2.1.2 which is working without issues

Can you externally backup config and other possibly mounted things and then fully rebuild the container, re pulling the image etc. Without any mounts, then the default config should appear, then mount the config file and check again.

I have followed your suggestions:

• Setting up my container from scratch, without any mounts, results in Dashy v3 working fine with the default config.
• Mounting the folder with my config to /app/user-data results again in a blank page, like before
• What ended up working: mounting an empty folder, so I get the default config. Then restoring my old config from the cloud, and saving it to "disk".

So it's working now. Thanks for your assistance :-)

[CrazyWolf13]

Awesome, great to hear!

[tradexsrl]

and sometimes is a problem of the firewall on synology nas or linux vm that block port 4000 or whatever

[CrazyWolf13]

Closing due to no response from original author and fixed for all the others.