-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Postgres FK constraint errors with fresh install #1605
Comments
Could be a bug, we'll try to reproduce the Postgres support isn't well tested. Surprising FKs would differ from SQLite to Postgres though. |
If it is any help I had turned on statement logging in Postgres and saw that it was complaining about the zeroGuid (
These are the FK constraints that were auto added by sliver.
As a temporary fix for me I removed them. I am not recommending this but if someone is in a pinch it is an option.
Update: Redacted the private key and etc. above but it is for a non-prod and non-internet facing env. :P |
Ah okay, we probably have an uninitialized GUID somewhere. |
Describe the bug
On a fresh install using postgresql backend I'm running into issues about foreign key constraints.
To Reproduce
Steps to reproduce the behavior:
Fresh install with postgresql backend then run
Same behavior happens when trying to add a new profile.
Expected behavior
Implants generates or profile is added as expected.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: