[Bug] Can't login to self host
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- authentication, backend
Research direction
Start by clarifying the AppFlowy version and deployment steps, and identify which login screen and server logs show the failure. Then trace the self hosted authentication flow and check whether the reported invalid email or password matches a reproducible failure. Done means reproducing the issue and identifying its cause; the report does not name files or tests.
Written by the indexing model from the issue text.
Description
Bug Description
I've been trying to log into myself We always use that using basically for the past several hours and I've tried different methods multiple ways to fix it but I haven't seemed
to see any results I haven't seen anything new changing it keeps telling me invalid password and or email even though my passwords are invalid are valid i've changed it in the back end I made the correct corrections I did everything I put the correct ports so on and so forth but it's still not allowing me logging and it's quite frustrating
How to Reproduce
I set up the workflow on an AWS EC2 server umm Amazon server We turn a reasonable amount of RAM I believe about two gig RAM before you run is the issue basically I set it up by configure figured all the ports and everything and then and I'll use yeah SSHI set up everything and I decided to use a browser and ports with the IP address of the on the server and run the app that's where I keep running into the password/email issue
Expected Behavior
Invalid email or password
Operating System
Windows 11
AppFlowy Version(s)
Not sure
Screenshots
No response
Additional Context
No response
- Dominant language
- Dart
- Stars
- 79.1k
- Forks
- 6.3k
- Avg merge
- 17h 29m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AppFlowy-IO/AppFlowy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AppFlowy-IO/AppFlowy#9147 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AppFlowy-IO/AppFlowy#9118 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AppFlowy-IO/AppFlowy#9094 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AppFlowy-IO/AppFlowy#9075 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AppFlowy-IO/AppFlowy#9074 ·
Maintainers usually reply within 1 day
All issues in AppFlowy-IO/AppFlowy
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
ccch1mneyyy/dsh-Go#1682 ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 1/5 Under an hour Newbie friendliness 76/100
pesaclarity/ujumbe-parsers#64 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
patarapolw/lingua_srs#278 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dreautall/waterfly-iii#890 · 1 comment ·
Maintainers usually reply within 1 day