github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-16 13:20:06 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Error 500 with Oauth2 and DISABLE_REGISTRATION #2667

New Issue
Open
opened 2025-11-02 04:43:55 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 04:43:55 -06:00
Owner
Copy Link

Originally created by @camlafit on GitHub (Dec 15, 2018).

  • Gitea version (or commit ref): 1.5.3
  • Git version:
  • Operating system: Debian stretch
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:
    2018/12/15 16:39:24 [...routers/user/auth.go:541 handleOAuth2SignIn()] [E] UserSignIn: could not find a matching session for this request

Description

If new registration is disbled and external connection allowed, we get a 500 error on callback url.
Workaround is to set on provider https://gitea/user/oauth2/[AuthnName] without callback part
or enable registration

Should be nice to redirect to association page to link oauth account with existing

Screenshots

Originally created by @camlafit on GitHub (Dec 15, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.5.3 - Git version: - Operating system: Debian stretch - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: 2018/12/15 16:39:24 [...routers/user/auth.go:541 handleOAuth2SignIn()] [E] UserSignIn: could not find a matching session for this request ## Description If new registration is disbled and external connection allowed, we get a 500 error on callback url. Workaround is to set on provider https://gitea/user/oauth2/[AuthnName] without callback part or enable registration Should be nice to redirect to association page to link oauth account with existing ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 04:43:55 -06:00
GiteaMirror commented 2025-11-02 04:43:56 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Apr 12, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 12, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:43:56 -06:00
Author
Owner
Copy Link

@jhult commented on GitHub (May 4, 2021):

This might be related to #5005.

@jhult commented on GitHub (May 4, 2021): This might be related to #5005.
GiteaMirror commented 2025-11-02 04:43:56 -06:00
Author
Owner
Copy Link

@pintman commented on GitHub (Mar 28, 2023):

experienced the same issue in gitea v1.19.0 go v1.20.2

@pintman commented on GitHub (Mar 28, 2023): experienced the same issue in gitea v1.19.0 go v1.20.2
GiteaMirror commented 2025-11-02 04:43:56 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Sep 29, 2024):

Can you check whether you are visiting a Gitea address that is not the one you input in the GitHub oauth2 application forms? I found that is a reason caused could not find a matching session for this request.

@lunny commented on GitHub (Sep 29, 2024): Can you check whether you are visiting a Gitea address that is not the one you input in the GitHub oauth2 application forms? I found that is a reason caused `could not find a matching session for this request`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/confirmed type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2667
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?