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

Login not working #3422

New Issue
Closed
opened 2025-11-02 05:12:29 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 05:12:29 -06:00
Owner
Copy Link

Originally created by @PKizzle on GitHub (Jun 3, 2019).

  • Gitea version (or commit ref): 1.8.2
  • Git version: 2.19.2
  • Operating system: GNU/Linux (arm7l)
  • 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:

Description

Running the arm6 build on arm7 I am unable to login.
I receive the following error messages:

[Macaron] PANIC: session(release): dial unix /opt/Gitea/gitea/data/sessions: connect: connection refused
/go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/session/session.go:199 (0x5432af)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:79 (0x527d4f)
/go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:157 (0x4ffc1f)
/go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:135 (0x4ff9c7)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:121 (0x527e8f)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:112 (0x536c8f)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/recovery.go:161 (0x536c74)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/logger.go:40 (0x52b41b)
/go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:157 (0x4ffc1f)
/go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:135 (0x4ff9c7)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:121 (0x527e8f)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:112 (0x53620f)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/logger.go:52 (0x5361f4)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/logger.go:40 (0x52b41b)
/go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:157 (0x4ffc1f)
/go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:135 (0x4ff9c7)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:121 (0x527e8f)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/router.go:187 (0x537d33)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/router.go:294 (0x5326df)
/go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/macaron.go:220 (0x52c67b)
/go/src/code.gitea.io/gitea/vendor/github.com/gorilla/context/context.go:141 (0x7e7307)
/usr/local/go/src/net/http/server.go:1995 (0x2a40d7)
/usr/local/go/src/net/http/server.go:2774 (0x2a6b33)
/usr/local/go/src/net/http/server.go:1878 (0x2a30f3)
/usr/local/go/src/runtime/asm_arm.s:868 (0x6f2e3)
2019/06/03 17:56:01 http: superfluous response.WriteHeader call from code.gitea.io/gitea/vendor/gopkg.in/macaron%2ev1.(*responseWriter).WriteHeader (response_writer.go:59)
[Macaron] 2019-06-03 17:56:01: Completed POST /user/login 500 Internal Server Error in 1.013625513s
Originally created by @PKizzle on GitHub (Jun 3, 2019). - Gitea version (or commit ref): 1.8.2 - Git version: 2.19.2 - Operating system: GNU/Linux (arm7l) - 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: ## Description Running the arm6 build on arm7 I am unable to login. I receive the following error messages: ``` [Macaron] PANIC: session(release): dial unix /opt/Gitea/gitea/data/sessions: connect: connection refused /go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/session/session.go:199 (0x5432af) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:79 (0x527d4f) /go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:157 (0x4ffc1f) /go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:135 (0x4ff9c7) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:121 (0x527e8f) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:112 (0x536c8f) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/recovery.go:161 (0x536c74) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/logger.go:40 (0x52b41b) /go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:157 (0x4ffc1f) /go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:135 (0x4ff9c7) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:121 (0x527e8f) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:112 (0x53620f) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/logger.go:52 (0x5361f4) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/logger.go:40 (0x52b41b) /go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:157 (0x4ffc1f) /go/src/code.gitea.io/gitea/vendor/github.com/go-macaron/inject/inject.go:135 (0x4ff9c7) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/context.go:121 (0x527e8f) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/router.go:187 (0x537d33) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/router.go:294 (0x5326df) /go/src/code.gitea.io/gitea/vendor/gopkg.in/macaron.v1/macaron.go:220 (0x52c67b) /go/src/code.gitea.io/gitea/vendor/github.com/gorilla/context/context.go:141 (0x7e7307) /usr/local/go/src/net/http/server.go:1995 (0x2a40d7) /usr/local/go/src/net/http/server.go:2774 (0x2a6b33) /usr/local/go/src/net/http/server.go:1878 (0x2a30f3) /usr/local/go/src/runtime/asm_arm.s:868 (0x6f2e3) 2019/06/03 17:56:01 http: superfluous response.WriteHeader call from code.gitea.io/gitea/vendor/gopkg.in/macaron%2ev1.(*responseWriter).WriteHeader (response_writer.go:59) [Macaron] 2019-06-03 17:56:01: Completed POST /user/login 500 Internal Server Error in 1.013625513s ``` <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/question label 2025-11-02 05:12:29 -06:00
GiteaMirror commented 2025-11-02 05:12:30 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jun 3, 2019):

Seems like there is an error with connecting to whichever session storage you are using, can you post your (appropriately sanitized) session config?

@techknowlogick commented on GitHub (Jun 3, 2019): Seems like there is an error with connecting to whichever session storage you are using, can you post your (appropriately sanitized) session config?
GiteaMirror commented 2025-11-02 05:12:30 -06:00
Author
Owner
Copy Link

@PKizzle commented on GitHub (Jun 3, 2019):

[session]
PROVIDER      = memcache
COOKIE_SECURE = true
@PKizzle commented on GitHub (Jun 3, 2019): ``` [session] PROVIDER = memcache COOKIE_SECURE = true ```
GiteaMirror commented 2025-11-02 05:12:31 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jun 4, 2019):

You don't need to post it, but do you have PROVIDER_CONFIG under [session]?

@techknowlogick commented on GitHub (Jun 4, 2019): You don't need to post it, but do you have `PROVIDER_CONFIG` under `[session]`?
GiteaMirror commented 2025-11-02 05:12:31 -06:00
Author
Owner
Copy Link

@PKizzle commented on GitHub (Jun 4, 2019):

Okay. So I installed redis and changed the gitea configuration accordingly. Now it is working.
Answering your question, before there was no PROVIDER_CONFIG entry.
All versions 1.7.x were running without issues using memcache.

@PKizzle commented on GitHub (Jun 4, 2019): Okay. So I installed redis and changed the gitea configuration accordingly. Now it is working. Answering your question, before there was no `PROVIDER_CONFIG` entry. All versions 1.7.x were running without issues using memcache.
GiteaMirror commented 2025-11-02 05:12:31 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jun 4, 2019):

It could be that because between 1.7.x & 1.8.x the session providers (an external library) were update to patch some issues, upstream may have changed the default value.

@techknowlogick commented on GitHub (Jun 4, 2019): It could be that because between 1.7.x & 1.8.x the session providers (an external library) were update to patch some issues, upstream may have changed the default value.
GiteaMirror commented 2025-11-02 05:12:31 -06:00
Author
Owner
Copy Link

@PKizzle commented on GitHub (Jun 5, 2019):

Just wanted to add that this was a configuration mistake. Memcache requires a PROVIDER_CONFIG entry. I should have used memory as session provider instead, which works with the default PROVIDER_CONFIG value. Now why did it work for gitea versions 1.7.x? It should not have worked for these versions either.
Anyway thanks for your support @techknowlogick

@PKizzle commented on GitHub (Jun 5, 2019): Just wanted to add that this was a configuration mistake. Memcache requires a `PROVIDER_CONFIG` entry. I should have used memory as session provider instead, which works with the default `PROVIDER_CONFIG` value. Now why did it work for gitea versions 1.7.x? It should not have worked for these versions either. Anyway thanks for your support @techknowlogick
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/question
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#3422
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?