mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-26 21:05:55 +03:00
[GH-ISSUE #579] GitHub Oauth returning 500 "Internal Server Error" when authenticating #293
Labels
No labels
android 🤖
assigned to core 🦹
bug 🐛
documentation 📚
documentation 📚
duplicate 🚫
external issue 🔼
external issue 🔼
feature request 🌟
funded on issuehunt 💵
help wanted 🆘
improvement request 🔨
improvement request 🔨
ios 🍎
mobile 📱
needs investigation 🔬
needs more info ℹ️
needs specs 📐
plugin idea 🔌
plugin idea 🔌
poll 🗳️
pull-request
question ❓
rewarded on issuehunt 🎁
security issue 🔑
won’t fix ❌
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/BoostNote-App#293
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @whophil on GitHub (Aug 10, 2020).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/579
Current behavior
When I try to create a new cloud storage (via the Boostnote Web App), it takes me to the GitHub Oauth login screen. After providing my username and password, it brings me back to a screen that just says "Internal Server Error." It works when I try to log in to a different user GitHub account - there just seems to be a problem with authenticating one specific account. I have tried revoking the OAuth permissions on GitHub to no avail.
Expected behavior
OAuth should work.
Steps to reproduce
This fails with a specific GitHub account and works with another.
Environment
@Flexo013 commented on GitHub (Aug 10, 2020):
@Rokt33r has more knowledge about these issues. I recommend you contact him on our Slack. That way you can get back on your way 😄
@Rokt33r commented on GitHub (Aug 10, 2020):
I'll investigate and try to fix this issue today.
@Rokt33r commented on GitHub (Aug 14, 2020):
This should be fixed by now. The problem was caused by using empty string for github name.