Activation is needed (again) during login #1440

New Issue

GiteaMirror · 2025-11-02T04:00:55-06:00

GiteaMirror commented

2025-11-02 04:00:55 -06:00

Originally created by @pwFoo on GitHub (Jan 11, 2018).

Hi,

I use Gitea behind a RevProxy with OTP (gitea.domain.tld) and can reach it direct with an internal URL (gitea.internal.domain.tld). I have to activate my account (again) during login or some other actions (I have to check...).

I don't know why the activated account have to be activated again by email verification. Why could the activation triggered again? Because of OTP (RevProxy remove the OTP, so gitea will just get username and password, login works fine) or different urls (gitea.domain.tld and gitea.internal.domain.tld)?

Any idea / hint how to check and solve that problem?

Originally created by @pwFoo on GitHub (Jan 11, 2018). Hi, I use Gitea behind a RevProxy with OTP (gitea.domain.tld) and can reach it direct with an internal URL (gitea.internal.domain.tld). I have to activate my account (again) during login or some other actions (I have to check...). I don't know why the activated account have to be activated again by email verification. Why could the activation triggered again? Because of OTP (RevProxy remove the OTP, so gitea will just get username and password, login works fine) or different urls (gitea.domain.tld and gitea.internal.domain.tld)? Any idea / hint how to check and solve that problem?

GiteaMirror added the type/question issue/stale labels 2025-11-02 04:00:56 -06:00

GiteaMirror closed this issue

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

GiteaMirror commented

2025-11-02 04:00:57 -06:00

@pwFoo commented on GitHub (Jan 11, 2018):

Auth method is ldap

@pwFoo commented on GitHub (Jan 11, 2018): Auth method is ldap

GiteaMirror commented

2025-11-02 04:00:57 -06:00

@lafriks commented on GitHub (Jan 11, 2018):

Most probably because you use multiple domains so when switching between them it asks for authorization again

@lafriks commented on GitHub (Jan 11, 2018): Most probably because you use multiple domains so when switching between them it asks for authorization again

GiteaMirror commented

2025-11-02 04:00:57 -06:00

@pwFoo commented on GitHub (Jan 11, 2018):

Each domain asks for login, but why I get the message that my user have to be activated by activation email (again)? My User is activated and active used.

User activation should be fired one time (after user creation / during first login).
But I don't know when / why user activation is triggered by gitea.

@pwFoo commented on GitHub (Jan 11, 2018): Each domain asks for login, but why I get the message that my user have to be activated by activation email (again)? My User is activated and active used. User activation should be fired one time (after user creation / during first login). But I don't know when / why user activation is triggered by gitea.

GiteaMirror commented

2025-11-02 04:00:57 -06:00

@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 04:00:57 -06:00

@stale[bot] commented on GitHub (Feb 23, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 23, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 11:57:27 -06:00

[PR #1440] [MERGED] Remove unused mutex field #15905

Sign in to join this conversation.