Skip to content
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

Admin account isn't created correctly with --config #71

aveao opened this issue Jan 26, 2019 · 2 comments


None yet
2 participants
Copy link

commented Jan 26, 2019

Describe the bug

When you just run ./writefreely --config and supply admin username and password, admin account isn't created correctly.

SQLite3 showing that there's no registered users

"User doesn't exist" on writefreely login

Output during --config

Steps to reproduce (if necessary)

Steps to reproduce the behavior:

  1. Download and extract writefreely 0.8.0 somewhere (tried on both /opt, used sudo all the way through, and on my home folder with no sudo)
  2. Run writefreely --config
  3. Do a setup that is similar to the log provided above or to the application configuration provided below, provide admin credentials.
  4. Run sqlite3 writefreely.db, run select * from users;
  5. Observe that there's no users.

Expected behavior

An admin user should've been created.

Application configuration

  • Single mode or Multi-user mode? Single mode
  • Database? SQLite
  • Open registration? no
  • Federation enabled? yes

Version or last commit:
0.8.0 for Linux, directly from releases, running on a Ubuntu 16.04 xenial server.

As a sidenote:

  1. I pasted my password on the box there and it was a 64 character a-zA-Z0-9 password, but it appeared there and writefreely gave it a checkmark (✔️).
  2. Doing ./writefreely --create-admin username:password with the same credentials did create the account, and now I can use writefreely.

@thebaer thebaer added the bug label Jan 26, 2019

@thebaer thebaer added this to the 0.8.1 milestone Jan 26, 2019

@thebaer thebaer self-assigned this Jan 26, 2019


This comment has been minimized.

Copy link

commented Jan 26, 2019

Thanks for reporting this! Looks like the adminInitDatabase() func was causing the app to exit early during the config process. I'll push a fix soon, and we'll do a bugfix release that includes the patch early this week.

@thebaer thebaer closed this in 08667d8 Jan 26, 2019


This comment has been minimized.

Copy link

commented Jan 27, 2019

Thanks for fixing this so quickly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.