-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Can't get firefly-iii to work #54
Comments
I've tried it locally using a Vagrant box and it seems to work just fine, even though not all the tables are perfect yet. If the tables already exist, be sure to remove all tables first, before you run the migration command ( I've done the following:
Please see if the SQL file and/or another attempt at running the migration will work. I'll see if I can find anything on this side. |
Thanks for the quick reply! With the reference SQL file the migration seems to work. I receive no errors anymore with the migration command. When trying to create a new account however, I only see the message: "Whoops, looks like something went wrong.". Do I try this again it says that the email-address has been taken. I guess this has something to do with my e-mail settings, but is it possible to get a more useful error message? |
At the moment, the error you see is a general "fallback" error which is used whenever something goes wrong. You should be able to find log files in the following directory:
There, the last messages should explain what happened. Most often it's the e-mail configuration. There is no fallback for that one: if sending an email fails you cannot retrieve the password in another way. I will create another issue to fix that, because relying on e-mail isn't very useful. If you want to see more debug information by default, you can edit
To re-register your own e-mail address, remove the single entry you should see in database table |
I installed firefly-iii on Ubuntu 14.04-LTS with nginx and mysql (via ajenti). First I installed composer globally, then I followed the install guide. I got some errors when running 'php artisan migrate --seed --env=production', fixed that with adding "doctrine/dbal": "~2.3" into the composer.json. Now I run into some errors, but don't know how to track this down. I tried this with a empty database, if I run the command again it says several tables already exists.
These are the errors I run into now:
[Illuminate\Database\QueryException]
SQLSTATE[HY000]: General error: 1025 Error on rename of './firefly@002diii/#sql-3d7_34d2' to './firefly@002diii/limit_repetitions' (errno: 150) (SQL: ALTER TABLE limit_repetitions CHANGE limit_id budget_limit_id INT UNSIGNED NOT NULL)
[PDOException]
SQLSTATE[HY000]: General error: 1025 Error on rename of './firefly@002diii/#sql-3d7_34d2' to './firefly@002diii/limit_repetitions' (errno: 150)
The text was updated successfully, but these errors were encountered: