IntenseFinance/firefly-iii
3
0
Fork 0
mirror of https://github.com/firefly-iii/firefly-iii.git synced 2025-02-16 10:14:58 -06:00
Code Issues Packages Projects Releases Wiki Activity

Update its_you_not_me.md

Browse Source
This commit is contained in:
James Cole 2022-03-31 04:21:50 +00:00 committed by GitHub
parent 55c82b2a0f
commit 8c2455e8dd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
.github/its_you_not_me.md vendored
View File

@ -1,15 +1,16 @@
# It's not you, it's me
Sometimes bugs reported to Firefly III are configuration and system problems on the user side.
Sometimes bugs reported to Firefly III are configuration and system problems on the user's side.
If you run into one of the following problems, there's a good chance it's not a Firefly III issue, but a configuration issue.
If you run into any of the following problems, there's a good chance it's not a Firefly III issue, but a configuration issue.
- ⚠️ Can't connect to the database when starting Firefly III
- ⚠️ Errors with missing app keys or encryption problems
- ⚠️ Can't login due to 419 errors
- ⚠️ Any 500 error when starting Firefly III
- ⚠️ Firefly III can't connect to the database when starting or the password is wrong, even though you're sure it's correct.
- ⚠️ Errors about a missing `APP_KEY` or other encryption/hash problems
- ⚠️ You can't login due to `419` errors (page expired)
- ⚠️ Any `500` error when starting Firefly III
- ⚠️ Any white page when starting Firefly III
- ⚠️ Time-out when starting Firefly III for the first time
- ⚠️ Firefly III does not work behind your reverse proxy
- ⚠️ You can't connect to the Data Importer due to 404's or authentication issues.
If you run into an issue like this, please start a [discussion](https://github.com/firefly-iii/firefly-iii/discussions) or chat on [Gitter.im](https://gitter.im/firefly-iii/firefly-iii). There's a good chance it's not a bug but something we can fix rather quickly :+1: