I migrated from a docker container to an LCX container. Therefore, I moved the data to the new system.
Everything was updated with the correct owner, just the config.json was not changed to the correct owner.
During changing data in the admin-area, the save throws and "400 Bad Request", but the UI shows, that the changed are there (also after a force refresh). The changed settings are active, until I update to the next version.
After chaning the owner to the correct user, saving is working.
I would recommend, that the response contain an information, that the config file is not writeable.
Originally created by @michaelmittermair on GitHub (Aug 10, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4834
I migrated from a docker container to an LCX container. Therefore, I moved the data to the new system.
Everything was updated with the correct owner, just the config.json was not changed to the correct owner.
During changing data in the admin-area, the save throws and "400 Bad Request", but the UI shows, that the changed are there (also after a force refresh). The changed settings are active, until I update to the next version.
After chaning the owner to the correct user, saving is working.
I would recommend, that the response contain an information, that the config file is not writeable.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @michaelmittermair on GitHub (Aug 10, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4834
I migrated from a docker container to an LCX container. Therefore, I moved the data to the new system.
Everything was updated with the correct owner, just the config.json was not changed to the correct owner.
During changing data in the admin-area, the save throws and "400 Bad Request", but the UI shows, that the changed are there (also after a force refresh). The changed settings are active, until I update to the next version.
After chaning the owner to the correct user, saving is working.
I would recommend, that the response contain an information, that the config file is not writeable.