-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Gophish attempts to recreate admin user every launch using mysql #948
Comments
I am currently getting the same issue, I'm also on Gophish 0.5.0 with a MySQL database backend. |
Thanks for the heads up on this! I’ll see if I can roll out a fix in the next day or so.
… On Feb 2, 2018, at 6:42 AM, Niek den Breeje ***@***.***> wrote:
I am currently getting the same issue, I'm also on Gophish 0.5.0 with a MySQL database backend.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This issue is also present in 0.4.0, but chooses to proceed instead of dying. Below are my logs.
|
This should be fixed as of 0f4ac70. Let me know if you run into any issues! |
Can you cut a new release for this bug fix? |
Is this already on 5.0 release ? |
I'm running 0.5.0 and am still having this issue. Using MySQL DB as well. |
@jasonmull This is because 0f4ac70 is merged in the mainline, but 0.5.0 is behind on the mainline. You should either build Gophish from source using its mainline, or wait for a new release. |
I'm setting up a new instance of gophish using the newly released 0.5.0, and seem to be running into a strange issue when using MySQL as a database backend. The first run works as expected, but if I try to kill and start gophish again, it attempts to create the admin user again, and fails with a duplicate key error. If I manually delete the admin user from the database, then I can rerun it again fine.
First run:
And everything works as expected. After killing it with "Ctrl+c" and rerunning:
config.json:
The text was updated successfully, but these errors were encountered: