github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-13 02:57:44 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Internal Server Error accessing urls on try.gitea.io #1348

New Issue
Closed
opened 2025-11-02 03:57:22 -06:00 by GiteaMirror · 16 comments
GiteaMirror commented 2025-11-02 03:57:22 -06:00
Owner
Copy Link

Originally created by @strk on GitHub (Dec 12, 2017).

Description

Clicked on "login" from https://try.gitea.io/gitea/gitea/issues/10, selected OpenID,
entered my URI, got redirected to my OpenID provider and back to get a 500 internal server error.

Upon trying again right now it worked, so the only useful information here would be in the server logs, if you keep them.

Originally created by @strk on GitHub (Dec 12, 2017). - Gitea version (or commit ref): 9f033bf - Can you reproduce the bug at https://try.gitea.io: - [x] Yes, https://try.gitea.io/user/login?redirect_to=/gitea/gitea/issues/10 ## Description Clicked on "login" from https://try.gitea.io/gitea/gitea/issues/10, selected OpenID, entered my URI, got redirected to my OpenID provider and back to get a 500 internal server error. Upon trying again right now it worked, so the only useful information here would be in the server logs, if you keep them.
GiteaMirror added the type/bug label 2025-11-02 03:57:22 -06:00
GiteaMirror commented 2025-11-02 03:57:23 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Dec 12, 2017):

Actually the Internal Server Error still occurs by just visiting this URL:
https://try.gitea.io/gitea/gitea/issues/10#issuecomment-1600

@strk commented on GitHub (Dec 12, 2017): Actually the `Internal Server Error` still occurs by just visiting this URL: https://try.gitea.io/gitea/gitea/issues/10#issuecomment-1600
GiteaMirror commented 2025-11-02 03:57:23 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Dec 12, 2017):

And no need for the anchor of course, so just https://try.gitea.io/gitea/gitea/issues/10

@strk commented on GitHub (Dec 12, 2017): And no need for the anchor of course, so just https://try.gitea.io/gitea/gitea/issues/10
GiteaMirror commented 2025-11-02 03:57:23 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Dec 12, 2017):

this ticket may have nothing to do with OpenID, anyway the ticket is visible from an anonymous window, only fails with 500 when I'm authenticated

@strk commented on GitHub (Dec 12, 2017): this ticket may have nothing to do with OpenID, anyway the ticket is visible from an anonymous window, only fails with 500 when I'm authenticated
GiteaMirror commented 2025-11-02 03:57:23 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Dec 31, 2017):

I was just hit again by the same issue, this time visiting https://try.gitea.io/gitea/gitea/pulls/5
this time as of ae9cc8f -- can anyone try to reproduce it or at least look at the logs ?

@strk commented on GitHub (Dec 31, 2017): I was just hit again by the same issue, this time visiting https://try.gitea.io/gitea/gitea/pulls/5 this time as of ae9cc8f -- can anyone try to reproduce it or at least look at the logs ?
GiteaMirror commented 2025-11-02 03:57:24 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Dec 31, 2017):

https://try.gitea.io/gitea/gitea/issues/10 is also still triggering it for me

@strk commented on GitHub (Dec 31, 2017): https://try.gitea.io/gitea/gitea/issues/10 is also still triggering it for me
GiteaMirror commented 2025-11-02 03:57:24 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Dec 31, 2017):

@lunny did you succeed in reading the server logs about this ? And/or could you reproduce it ?
(I'm not sure if the chat bridge is still working, and I don't have access to discord)

@strk commented on GitHub (Dec 31, 2017): @lunny did you succeed in reading the server logs about this ? And/or could you reproduce it ? (I'm not sure if the chat bridge is still working, and I don't have access to discord)
GiteaMirror commented 2025-11-02 03:57:24 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Dec 31, 2017):

Should be related to the openid auth, with my regular user it works fine

@tboerger commented on GitHub (Dec 31, 2017): Should be related to the openid auth, with my regular user it works fine
GiteaMirror commented 2025-11-02 03:57:24 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Dec 31, 2017):

Can you extract anyting meaningful from the logs about this ? I don't see how authentication method should affect visiting an issue or pull request. Also my user is non-admin, can you try with a non-admin user ? There might also be other things which are different for me, maybe I'm a partecipant in those issues...

@strk commented on GitHub (Dec 31, 2017): Can you extract anyting meaningful from the logs about this ? I don't see how authentication method should affect visiting an issue or pull request. Also my user is non-admin, can you try with a non-admin user ? There might also be other things which are different for me, maybe I'm a partecipant in those issues...
GiteaMirror commented 2025-11-02 03:57:25 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Dec 31, 2017):

I've just tried logging out and logging-in again, this time via GitHub. The problem persists, I still get a 500 visiting any issue of gitea/gitea

@strk commented on GitHub (Dec 31, 2017): I've just tried logging out and logging-in again, this time via GitHub. The problem persists, I still get a 500 visiting any issue of gitea/gitea
GiteaMirror commented 2025-11-02 03:57:25 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 31, 2017):

Still cannot reproduce

@lunny commented on GitHub (Dec 31, 2017): Still cannot reproduce
GiteaMirror commented 2025-11-02 03:57:25 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Dec 31, 2017):

@lunny I can reproduce that when logged in with strk user on try.gitea.io

@lafriks commented on GitHub (Dec 31, 2017): @lunny I can reproduce that when logged in with strk user on try.gitea.io
GiteaMirror commented 2025-11-02 03:57:25 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Dec 31, 2017):

Next obstacle seems to be that @lunny is unable to read the logs of try.gitea.io -- can anyone else access those logs ? Or I'd file another issue just for that, as it seems very important to me to be able to read logs of a try server, often used to showcase bugs...

@strk commented on GitHub (Dec 31, 2017): Next obstacle seems to be that @lunny is unable to read the logs of try.gitea.io -- can anyone else access those logs ? Or I'd file another issue just for that, as it seems very important to me to be able to read logs of a `try` server, often used to showcase bugs...
GiteaMirror commented 2025-11-02 03:57:26 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 9, 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 (Feb 9, 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 03:57:26 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 11, 2019):

@strk is this still a problem?

@lunny commented on GitHub (Feb 11, 2019): @strk is this still a problem?
GiteaMirror commented 2025-11-02 03:57:27 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Mar 29, 2019):

The URL is now a 404 so I've no idea if the problem still exists

@strk commented on GitHub (Mar 29, 2019): The URL is now a 404 so I've no idea if the problem still exists
GiteaMirror commented 2025-11-02 03:57:27 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 29, 2019):

The repo has been recreated so that that issue is lost.

@lunny commented on GitHub (Mar 29, 2019): The repo has been recreated so that that issue is lost.
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 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#1348
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?