Just to add to this. I was having the same issue with nginx restarting.
Stopping Bitwarden and running:
chmod -R 704 /opt/bitwarden/bwdata/nginx
Then restarting BW, sees to have resolved the issue.
I had a similar issue when updating a couple weeks ago, if I remember correctly I was going to 2025.9 and I had the nginx container stuck restarting. I was in a hurry and needed the passwords so I just rolled back the VM to an earlier backup.
I am not super skilled in Linux so I need to keep this post monitored to be sure that I solution is released before trying to update again. I would like to avoid the need for manual adjustments after an update.
I’m not sure about your timeline, as server version 2025.9.0 only was released 4 days ago…
And I think, for some people this already is resolved. (e.g. here and here…)
I said “if I remember correctly” exactly because I mostly don’t. I was probably landing on v2025.8 and it happened.
I am glad to see there is a fix. I am away for work and I learned the hard way to not update my stuff remotely when I am away from home. I will try again at the end of the month and report back.
the messages you linked are not a solution, as I don’t intend a solution when I need to manually intervene using the command line. that’s a workaround. the software has an update feature which should just work without breaking functionality.
I don’t want to argue with you now, but if something was configurable more widely in the past and doesn’t work now in newer versions, I’m not sure if those configurations will be automatically changed by any update.
I definitely also don’t want to argue, I also feel like we could never understand each other 100% due to myself not being a native english speaker. I feel like I did not understand what you mean in your last post, and I feel like you missed what I had meant before.
let’s just agree on being happy cause it was solved 
2 Likes