Config not saving

[HighSunMurder]

Environment

Self-Hosted (Docker)

System

Ubuntu

Version

Current

Describe the problem

Any changes i make in dashboard i save to disk via UI, If i reboot the server these changes are gone and dashy is vanilla / default

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

[ulysserevient]

Same problem here !
Unable to save conf.yml from the UI
The backup file is created, but the conf.yml isn't saved !

[HighSunMurder]

Any suggestions on fix other than blowing it away and starting over? Thx

…

On Fri, Mar 31, 2023 at 6:12 AM ulysserevient ***@***.***> wrote: Same problem here ! Unable to save conf.yml from the UI The backup file is created, but the conf.yml isn't saved ! — Reply to this email directly, view it on GitHub <#1147 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AY54QDJWP4ORNX4ZISXTZR3W62UZFANCNFSM6AAAAAAWAO6KTE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ulysserevient]

I still can't save the conf file from the gui
is there a solution ?

[rongalbraith]

I have had the same issue. I get an error "AxiosError: Network Error". This wasn't always happening and I wasn't sure why.

Anyway, I was a little lazy in my implementation and had just used default (root) login to run the Dashy container. I've since switched it to using a non-root user (changed ownership of the folder structure) and everything is working fine now. Shouldn't have made a difference but I'll keep this updated in case I have any further issues.

[minisculemarch]

Same issue, regarding the file not saving but the backup is created. Rebuild also fails randomly, 503. I've found it easier to simply edit the conf file manually the restart the docker container.

[rongalbraith]

So, for me the answer was to implement a non-root installation for the container. Not sure why it worked but there's obviously some conflict somewhere that doesn't occur when you're container is running under a non-root user.

Just added UID and GID environment variables:
# Set any environmental variables
environment:
# Specify your user ID and group ID. You can find this by running id -u and id -g
- UID=1001
- GID=1001

Bear in mind that "1001" was my default user and your user may be different. Quick chown -R in the terminal for the folders where I was storing the persistent volume for Dashy, bounced the container and everything has been fine since.

[Glitch3dPenguin]

I have been having a similar issue. I’m going to give this a shot as well and see if I make and progress. Thanks for the recommendation!

[matteo-martinelli]

I have the same issue. Any kind of change is not update. Backups are made, but any change is effective.

[ulysserevient]

Hi,
I've tried to change UID and GID with non-root user, but problem persists !

[offline09]

Hi, I am having the same problem, set all my links up then boom, everything gone. Tried the non-root user change, and still broken.

[strangedesign13]

Not sure if this is the intended design of dashy or if there is a bug, but what I finally found worked had nothing to do root owner. After editing hit “Save to Disk”, then open “Update Configuration” (the wrench icon) and then select “Rebuild Application”. After it completes, I have had no issues with refreshing the dashboard, closing it and repointing it.

While saving a config doesn’t trigger the rebuild, I’m not sure but this has solved the issue for me.

[avaaum]

i had this same issue that caused me to loose all my edits multiple times. edited fonts and colors did not stick after saving to disk multiple times, but menus, menu items and icons did. @strangedesign13's workaround above finally did the trick. i feel the expected behavior is for the "save to disk" function to trigger the "rebuild application" function. fwiw i'm using ff/librewolf and everything is up to date. plz look into this. thx again for your work. dashy is awesome 💜

[Lissy93]

I think there may be a several different issues here,

Possible Issue 1: Unable to call save endpoint from CDN/static server

If you're running Dashy on a static host, like Vercel, then there's no server-side code to actually save the config, re: #1465 (this is outlined bit more in the docs)

Possible Issue 2: Unable to save

In Docker, double check that the file isn't read-only, and that the container actually has permissions to modify it. You shouldn't really be running it as a root user, and I'm not sure if it will work if you do

Possible Issue 3: Saved but not updating

After saving, the frontend will recompile, which may take a couple seconds (or a bit longer on a Pi or low-powered device). If it doesn't recompile, you can manually trigger a re-build.

None of the above?

If you're still having issues, if you could share the following with me, it'll help me look into it further:

• If you open the conf.yml file, can you see your changes?
• When you save, are there any errors in the browser console (see: how to open browser console)
• Are there any errors in your Docker logs?

[CrazyWolf13]

Hi
This problems seems to be related to dashy not automatically rebuilding on changes (#1147 (comment)) , see #1479 and #1290 (comment)
A new release has just been published, which should fix this issue, so please upgrade to the latest version.
If this is not the case just respond back to this ticket and I'll reopen this issue.
Thanks and have a nice day.

[wilcomir]

Hello,

I am still having issues with this - saving the configuration via the gui does not work properly.

I am using docker-compose, setting UID and GID to my user (1000:1000). I am passing through a whole folder to the container, permissions of the folder and all the files within are correct.

When I make a modification from the GUI, a backup file is created - therefore dashy can write to the folder - but the new conf.yaml is... not new, it's just the same. I see no error in the docker log, when I hit save a rebuild is correctly triggered, no error in the browser console as well.

I tried all permutations that I could think of, running the container without UID/GID, changing ownership of the folder to root:root, making the folder & contents chmod 777...

I am unsure how to proceed, I love this project and I am willing to perform any troubleshooting that might be necessary.

I have performed a bit of debugging, and noticed that even if I run the container with UID:GID set, the backup files are still saved as root. Inside the container itself, I see that the 1000:1000 files are (presumably) correctly mapped to user node, including conf.yaml

[rawGH]

I have the same exact issue. Dashy works. Installation/Configuration is done properly. I've been configuring Dashy for a couple of days now with little to no issues. However I am not able to edit config file via GUI. I mean I could do it the first time but never again after that. Changes are never really saved, even though saving confirmation is shown as successful.
I've tried waiting, reloading and rebuilding with no success.
Ver. 2.1.2
Edit: temp solution: edited conf.yml manually (docker).
Edit2: did some light observing. Upon saving, two files are affected: seems that the old config version is saved into conf.xxx.backup.yml and conf.yml. In any case, it doesn't look like a permission problem, as files are written/updated.

[shalithasuranga]

I had the same issue. Now, I just do preview changes -> save to disk from the JSON editor. This workaround works very well and is easy 🎉

[rawGH]

I had the same issue. Now, I just do preview changes -> save to disk from the JSON editor. This workaround works very well and is easy 🎉

I've tested, but it does not work for me. I can edit "tree" (eg changing the order of sections) and save then, it works. Changes might require rebuild or reload page, but it works. The bug appears only when "code" is used and changed anything (even a string or something), it's never saved, using "Preview Changes" does nothing in this case.
When checking the actual files upon saving, two are affected. Backup and normal conf.yml, but contents are the same, as is the timestamp of both files, unfortunately the saved version is the previous one, so no actual changes were stored.

[jonathantalkshw]

I just found out that when you click "tree" which give you a dropdown menu, and the other options is "code" and "preview", click on code, then make some changes, then hit "preview changes", then "save to disk". but I have not tried without changing the menu next to the undo & redo button before doing the preview changes, that could work. and the way I did actually updated it, even if I refreshed my dashy page.

[Lissy93]

Try V3, there should be no more issues with this anymore

[rawGH]

Did a quick recreate docker to v3. Tested for about 10min, all seems to be working now. Thanks L.