Replies: 2 comments
-
Status code 504 is a Gateway Timeout error. As far as I know, stash does not return this status code in general, which suggests that you're using a reverse proxy or something else not covered in your description. Can you share more about your running environment? |
Beta Was this translation helpful? Give feedback.
-
By any chance are you using stash over a network share? I had the same 504 and per @WithoutPants suggestion I accessed stash directly instead of via a reverse proxy. The error I got was "Database is locked" instead of a 504. Worth noting that stash worked perfectly fine on nfs but I had to switch because I was getting stale file handles. Now I don't get those and instead have the db locking issue. Without going further off topic, more about your env would be good and in general, sqllite apps and network shares can really be hit or miss |
Beta Was this translation helpful? Give feedback.
-
Migration failed
The following error was encountered while migrating the database:
Response not successful: Received status code 504
To Reproduce
Steps to reproduce the behavior:
Expected behavior
migrate success
Screenshots
Stash Version: (from Settings -> About):
upgrade from v24.3 to v25
Desktop (please complete the following information):
Beta Was this translation helpful? Give feedback.
All reactions