-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
beta.38 - nginx-ui wont start anymore #673
Comments
Hi @jiriteach, If you have an SQLite editor, open the database.db under /usr/local/etc/nginx-ui, clear the sites table, and restart the nginx-ui. Normally, this issue should not happend. |
Perfect - thanks. Looks like its worked. Will run some tests. |
Yes, I added a unique constraint in Line 5 in bb02d7b
since beta.37. If the sites table has more than one row with the same path, the db migration will fail, so you have to clear the table manaully. |
This problem may be caused by the soft delete introduced in the previous version, I'm sorry about that. |
No worries - is there any issue with clearing the sites table? Does it have any affect? I see all my sites look fine so clearing it didnt break anything? |
No side effects if the database is created in previous versions. If you clear the database since beta.37, you will lose the category and the sync nodes settings of the site. |
Upgraded to beta.38 and the update hung.
Checked the service and it was stopped. Trying to restart - just errors.
How do I restart? I tried re-installing and no luck either.
Here is the log from /var/log/syslog
Looks like the error -
2024-10-28T23:29:38.003289+13:00 moober nginx-ui[51777]: 2024-10-28 23:29:38#011FATAL#011model/model.go:76#011UNIQUE constraint failed: sites.path
The text was updated successfully, but these errors were encountered: