[BUG] Version 4.3.1 - Editing dashboard and saving to disk error

[tessierp]

Environment

Self-Hosted (Docker)

System

Docker 29.5.3

Version

4.3.1

Describe the problem

Editing the dashing pressing OPTIONS -> EDIT MODE :

1. Go to any of my section and select ADD NEW ITEM
2. I will enter the details I need for the new item
3. Press SAVE TO DISK
4. Results in error : An error occurred saving config
5. I went and checked the logs through portainer for dashy, no logs showing the error

I have checked for permission issues, making sure that the data container has the required rights.. These are the same rights prior to version 4.3.0 and it has always worked.

Additional info

No response

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

[lissy93]

Hmm, that's weird, nothing relating to the server or config changing has changed in recent versions. Can you remember which version this last worked for you with?

Interestingly, you will only see that toast message if the server endpoint did get called and returned a non-200. In which case there will be more details about the error both in the server-side logs, as well as the browser console. So if you could take another look at your Portainer logs, this would really help.

As for the browser logs, it's usually F12, but more details here. Then in the network tab, try save again, and look at the response from the save-config endpoint. This will have the error message from the server-side.

I guess you've checked https://dashy.to/docs/troubleshooting/#config-not-saving ?

[lissy93]

I've included an update in #2203 which is now merged and released in Dashy 4.3.3, which will show you the server error in the client-side console. It will basically be same as what you see in your docker logs, but should help you fix your issue :) I guess permissions error.

After update, re-trigger the save error, and check both server and client logs, as well as the info in Config --> Debug Info.

Going to close the issue for now, as there's not enough info here for me to look into it. But if you can provide more info and the full logs, then feel free to comment below and I'll reopen/try to help.

[tessierp]

Hmm, that's weird, nothing relating to the server or config changing has changed in recent versions. Can you remember which version this last worked for you with?

Interestingly, you will only see that toast message if the server endpoint did get called and returned a non-200. In which case there will be more details about the error both in the server-side logs, as well as the browser console. So if you could take another look at your Portainer logs, this would really help.

As for the browser logs, it's usually F12, but more details here. Then in the network tab, try save again, and look at the response from the save-config endpoint. This will have the error message from the server-side.

I guess you've checked https://dashy.to/docs/troubleshooting/#config-not-saving ?

Hi there. I added the last version that worked for me as I regressed and tried but I think I forgot to send the response... I tried version 3.3.0 and I do not have the problem, I'm able to save without any issues without changing the permissions. I also have checked the permissions and everything is as it should be as far as I can see. I tried 3.3.0 just now and I'm able to save without any changes to the permissions. As soon as I update to latest, it fails.

With 4.3.3 I'm getting a permission issue which I do not have in 3.3.0 despite having the right permissions set for the docker container and the file system. This is very strange..

[17:19:16] Failed to save config. Unable to backup conf.yml: Error: EACCES: permission denied, copyfile 'user-data/conf.yml' -> 'user-data/config-backups/conf-1781385556808.backup.yml'
[17:24:41] Failed to save config. Unable to backup conf.yml: Error: EACCES: permission denied, copyfile 'user-data/conf.yml' -> 'user-data/config-backups/conf-1781385881553.backup.yml'

I would be inclined to agree that it is a permissions issue if 3.3.0 would not work either however, 3.3.0 works while 4.3.4 does not without any changes..

Here is my current config

`# Dashy
dashy:
deploy:
placement:
constraints:
- node.hostname==PTR1-PrimeSvr
restart_policy:
condition: any
max_attempts: 100
delay: 60s
window: 60s
healthcheck:
disable: false
image: lissy93/dashy:latest
ports:
- 9180:8080
volumes:
- dashy-data:/app/user-data/
environment:
- PUID=${PUID:-500}
- PGID=${PGID:-500}
- TZ=${TIMEZONE:-America/Toronto}
- NODE_ENV=production
networks:
- tools-net

Extras

volumes:
dashy-data:
external: true

networks:
tools-net:
driver: overlay
attachable: true
`

[lissy93]

Ah, I see the issue now - it's permission error on user-data/config-backups/ which is where backups of configs are made (so you can roll back if needed).

Anyway, the normal permissions command will fix this: sudo chown -R 1000:1000 /path/to/your/user-data
Or add user: "1000:1000" in your dashy service in your compose

Or, you can disable config backups if you don't want or need them, by setting DISABLE_CONFIG_BACKUPS=true

More detailed fix is in troubleshooting guide: https://dashy.to/docs/troubleshooting/#config-not-saving

---

3.3.0 works while 4.3.4 does not without any changes

Yep, 4.0.0 onwards switched to no-root container. It was major version bump with breaking changes.
See release notes in #2093
Similar issue mentioned in #2096 and #2097

[tessierp]

Here is my config

Ah, I see the issue now - it's permission error on user-data/config-backups/ which is where backups of configs are made (so you can roll back if needed).

Anyway, the normal permissions command will fix this: sudo chown -R 1000:1000 /path/to/your/user-data

Or, you can disable config backups if you don't want or need them, by setting DISABLE_CONFIG_BACKUPS=true

I'm not sure if this could be the issue but, as you can see with my config above, anything docker related uses user ID 500 which is what I have setup every where and what I also works with 3.3.0... I'm wondering is there anything in version 4.x that forces a check for user ID 1000 ? IF that is so, it could be the reason. Otherwise, I am really not sure why I would be getting a permissions issue as I am confident the permissions are OK on my side and especially that version 3.3.0 works. For now I'll disable backups... FYI : I have a lot of accumulated backups in that folder I guess from previous versions. Just out of curiosity is there a way to keep only the last 5 backups?

[tessierp]

Yep, 4.0.0 onwards switched to no-root container. It was major version bump with breaking changes.
See release notes in #2093
Similar issue mentioned in #2096 and #2097

Hmm I'm not sure I understand the "no-root" container part.. But I guess this comes down to a breaking change from 3.3.0; if I have to use 1000:1000 for the user that wont work for me since it would break other things. I guess I'll have to disable backups for now.

[lissy93]

Upto 3.3.0 the container ran as root.
It's best practice to NOT do that, so from 4.0.0 onwards we now use the correct ownership standards, of UID 1000 by default. Pls check the docs, issues and release notes for all the info.

So, you need to either:

Option 1) run container with your own UID

services:
    dashy:
      user: "500:500"

Option 2) OR set the right owner on the file

sudo chown -R 1000:1000 /your/user-data

If you want to change anything within Dashy, make a fork, and build your own container from that.
But like I said, this isn't something I'm able to do from my end, without breaking standards or causing hassle for other users.

[tessierp]

Upto 3.3.0 the container ran as root. It's best practice to NOT do that, so from 4.0.0 onwards we now use the correct ownership standards, of UID 1000 by default. Pls check the docs, issues and release notes for all the info.

So, you need to either:

Option 1) run container with your own UID

services:
dashy:
user: "500:500"
Option 2) OR set the right owner on the file

sudo chown -R 1000:1000 /your/user-data

If you want to change anything within Dashy, make a fork, and build your own container from that. But like I said, this isn't something I'm able to do from my end, without breaking standards or causing hassle for other users.

Sorry if I gave the impression that I was complaining. I was merely trying to understand the issue as I run many other docker apps with the same setup and I guess many must be running their containers as root I guess; but I guess I use environment variables PUID and PGID and set those to 500 and that is what I have for most containers to set the user that has "root privileges". Anyway, thanks for the help, today I just learned you can set a user: "500:500" which is something I didn't know before. :)

And I have no intention of forking Dashy as I am involved in other things and am too busy and happy with what you build, just couldn't figure out what changed. Thanks again.