Internal Error – 500 – when trying to log in with 2FA enabled #1360

New Issue

GiteaMirror · 2025-11-02T03:57:48-06:00

GiteaMirror commented

2025-11-02 03:57:48 -06:00

Originally created by @FrostyPenguin on GitHub (Dec 13, 2017).

Gitea version (or commit ref): master: c06cc74
Git version: 2.15.1
Operating system: GNU (Running on arm64, distribution: Arch Linux ARM)
Database (use '[x]'):
PostgreSQL
MySQL
MSSQL
SQLite
Can you reproduce the bug at https://try.gitea.io:
Yes (provide example URL): Sign in page
No
Not relevant
Log gist: GitHub gist

Description

After I updated my Gitea installation to the newest build in master (2017-12-13 18:00 UTC+1) signing in with 2FA was broken. Surprisingly, this is not a “local” issue as logging in to try.gitea.io with an already existent account that's got 2FA enabled did not work either.

I tried restarting my Browser (Firefox 57.0.2) in Safe Mode (with uMatrix, uBlock, and HTTPSEverywhere disabled), but that didn't help. So it must be a problem with some newer commits to Gitea's master branch.

Even though at first sight this might look like #1851, it definitely is a new and reproducible bug as “downgrading” my Gitea binary to 1.3.1 solved the problem for me.

Screenshots

I'm not sure if you this will help you, but sure… here's a screen cast.

https://streamable.com/4jv6u

Originally created by @FrostyPenguin on GitHub (Dec 13, 2017).  - Gitea version (or commit ref): [master: c06cc74](https://github.com/go-gitea/gitea/commit/c06cc740dea46f3aff58e0eded4208232bb5902d) - Git version: 2.15.1 - Operating system: GNU (Running on arm64, distribution: Arch Linux ARM) - Database (use '[x]'): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [X] Yes (provide example URL): [Sign in page](https://try.gitea.io/user/login?redirect_to=) - [ ] No - [ ] Not relevant - Log gist: [GitHub gist](https://gist.github.com/FrostyPenguin/88c9a807051fd95ca660289fd31d1288) ## Description After I updated my Gitea installation to the newest build in [master](https://dl.gitea.io/gitea/master/) (2017-12-13 18:00 UTC+1) signing in with 2FA was broken. Surprisingly, this is not a “local” issue as logging in to try.gitea.io with an already existent account that's got 2FA enabled did not work either. I tried restarting my Browser (Firefox 57.0.2) in Safe Mode (with uMatrix, uBlock, and HTTPSEverywhere disabled), but that didn't help. So it must be a problem with some newer commits to Gitea's master branch. **Even though at first sight this might look like #1851, it definitely is *a new and reproducible* bug as “downgrading” my Gitea binary to 1.3.1 solved the problem for me.** ## Screenshots I'm not sure if you this will help you, but sure… here's a screen cast. https://streamable.com/4jv6u

GiteaMirror added the type/bug label 2025-11-02 03:57:48 -06:00

GiteaMirror closed this issue

2025-11-02 03:57:48 -06:00

GiteaMirror commented

2025-11-02 03:57:49 -06:00

@thehowl commented on GitHub (Dec 30, 2017):

I am working on this now. After 8 steps of git bisecting, I traced back the culprit to b7ebaf6d20. Writing it down here in case I just go to sleep in a few minutes and forget about this issue entirely.

@thehowl commented on GitHub (Dec 30, 2017): I am working on this now. After 8 steps of git bisecting, I traced back the culprit to b7ebaf6d2078cbf4de00d0782be8bc1b1de644bb. Writing it down here in case I just go to sleep in a few minutes and forget about this issue entirely.

GiteaMirror referenced this issue

2025-11-02 11:56:40 -06:00

[PR #1360] [MERGED] fix: remove `str2html` from org full name #15876

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#1360