Codeberg/Community
54
325
Fork
You've already forked Community
12

Email Activation Fails #1992

Closed
opened 2025年06月22日 11:47:56 +02:00 by ZealousCynic · 3 comments

Comment

I use a proton email account, and for whatever reason whenever I try to activate the email, it'll fail with a 500 Internal Server Error.

It leaves my email activation dashboard as shown below for a while, before presumably timing out and letting me go through the process again. Which is quite annoying:

image

NB: I cropped out the left part of the image, so that's why it looks a bit strange.

Browser debugging tools do not seem able to provide me much more information.

Best guess on my part is that it might be related to catching throwaway email domains to guard against spam, as IIRC seeing it mentioned in another issue here... But that might be me making up false memories as I can't seem to find it anymore.

In any case, should someone pick this up, it'd be appreciated on my end - I was quite excited to explore an alternative to the incumbents with regards to repo hosting.

Kind regards

### Comment I use a proton email account, and for whatever reason whenever I try to activate the email, it'll fail with a 500 Internal Server Error. It leaves my email activation dashboard as shown below for a while, before presumably timing out and letting me go through the process again. Which is quite annoying: ![image](/attachments/9a49a60f-ca77-4a8b-807d-0f950fa2383d) NB: I cropped out the left part of the image, so that's why it looks a bit strange. Browser debugging tools do not seem able to provide me much more information. Best guess on my part is that it might be related to catching throwaway email domains to guard against spam, as IIRC seeing it mentioned in another issue here... But that might be me making up false memories as I can't seem to find it anymore. In any case, should someone pick this up, it'd be appreciated on my end - I was quite excited to explore an alternative to the incumbents with regards to repo hosting. Kind regards

Hi, I've experienced the same issue.

Do you happen to have capital letters in you email? Proton allows it, and letter case should be irrelevant for email infrastructure as a whole, but it is ill-advised as some software may fail to handle it.

I solved it by deleting my account and re-making it with the same email written in lower case.

Hi, I've experienced the same issue. Do you happen to have capital letters in you email? Proton allows it, and letter case should be irrelevant for email infrastructure as a whole, but it is ill-advised as some software may fail to handle it. I solved it by deleting my account and re-making it with the same email written in lower case.
Owner
Copy link

Thank you. The problem with upper/lower case was a good hint. I was able to reproduce the issue and made a qualified report to forgejo/forgejo#8354

The problem will probably be resolved soon.

Thank you. The problem with upper/lower case was a good hint. I was able to reproduce the issue and made a qualified report to https://codeberg.org/forgejo/forgejo/issues/8354 The problem will probably be resolved soon.

@SergeTheEngi wrote in #1992 (comment):

Hi, I've experienced the same issue.

Do you happen to have capital letters in you email? Proton allows it, and letter case should be irrelevant for email infrastructure as a whole, but it is ill-advised as some software may fail to handle it.

I solved it by deleting my account and re-making it with the same email written in lower case.

While it's late, I wanted to confirm that yes, I have capital letters on the email account I registered with.

Like you, the activation issue could be resolved by switching to an account in all lowercase.

I'll try to keep this in mind for future registrations

@fnetX wrote in #1992 (comment):

Thank you. The problem with upper/lower case was a good hint. I was able to reproduce the issue and made a qualified report to forgejo/forgejo#8354

The problem will probably be resolved soon.

Thank you for taking the time to look at this.

@SergeTheEngi wrote in https://codeberg.org/Codeberg/Community/issues/1992#issuecomment-5551715: > Hi, I've experienced the same issue. > > Do you happen to have capital letters in you email? Proton allows it, and letter case should be irrelevant for email infrastructure as a whole, but it is ill-advised as some software may fail to handle it. > > I solved it by deleting my account and re-making it with the same email written in lower case. While it's late, I wanted to confirm that yes, I have capital letters on the email account I registered with. Like you, the activation issue could be resolved by switching to an account in all lowercase. I'll try to keep this in mind for future registrations @fnetX wrote in https://codeberg.org/Codeberg/Community/issues/1992#issuecomment-5651753: > Thank you. The problem with upper/lower case was a good hint. I was able to reproduce the issue and made a qualified report to forgejo/forgejo#8354 > > The problem will probably be resolved soon. Thank you for taking the time to look at this.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1992
Reference in a new issue
Codeberg/Community
No description provided.
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?