What is GitLab Technical Support's e-mail address?

I want to forward en e-mail to them so that they can fix a 404. A ticket is definitely not the best way to do this, and is overkill since I don’t need them to keep me up-to-date about it.

mailto:support@gitlab.com is useless.


I found this by checking the respondent to an e-mail sent to support@gitlab.com in its message header - it’s techsupport@gitlab.com, but with a sub/plus-address added.

Please refrain from emailing Support directly, as tickets or emails received this way will not be seen by a human who can assist you or report/address the issue.

All support tickets must be associated with an organization that holds a valid GitLab subscription. If you are not pre-listed, this will result in a rejection message. (Source)

If you are reporting an issue that is impacting GitLab.com availability or usability, or you’ve discovered a bug affecting self-managed instances, please open an issue: https://gitlab.com/gitlab-org/gitlab/-/issues/new

If you are seeking help with your GitLab Free Tier Account or Community Edition installation, please note that the GitLab Support Team is unable to directly assist with these issues.


Thanks. How could I forward an e-mail using that method, though? It doesn’t appear to allow the user to upload attachments, so I can’t even provide a .eml file.

Considering that 404 pages provide debug info but I can’t provide the (in my case, e-mail) origin will mean nobody will report dead hyperlinks in messages sent via e-mail.


Yes, that occurs when messaging

but not when

is sent a message. No response is sent.

Considering that you’re part of https://forum.gitlab.com/g/gitlab-team, can you remediate this?

If your user and email are associated with an organization that has a valid GitLab subscribtion, you can use https://support.gitlab.com/hc/en-us/requests/new to open support tickets and add attachments.

If you’re not a paying customer, anything you send to support (via email or Support Portal) will not be seen by a human - do not expect a response.

Considering that you’re part of https://forum.gitlab.com/g/gitlab-team , can you remediate this?

I’m actually an alumni of the GitLab Support team. There is nothing to “remediate” here, as GitLab Support does not offer regular email support and GitLab Support is only available to paying customers. This is mentioned on our Subscribtion Agreement and Support page. If you’re a paying customer, please use the Support portal for anything ticket related and refer to the following resources:

To get help or report problems as a community member without a paid license or subscribtion, your options are:

You can paste or attach any relevant information from the email into a forum post or issue.

1 Like

I’m curious which URL is affected, throwing a 404. Mind sharing it here?


@gitlab-greg, I meant that I suggest GitLab send the “no responses via e-mail without going through the contact form first” auto-response via all e-mail addresses not explicitly for internal use that aren’t monitored, to prevent people like me thinking we’ve found an address that is monitored.

People are dumb. We don’t bother to read agreements and disclosures. It’s just a suggestion, with some decent context as rationale.

@dnsmichi, I can’t upload the .eml because

Sorry, the file you are trying to upload is not authorized (authorized extensions: jpg, jpeg, png, gif, ico).

appears when I attempt to. However, I just re-evaluated all of the links in the original e-mail message, and they work.

I believe the link that was broken was Automatic Logouts Are Too Frequent (#121569) · Issues · GitLab.org / GitLab · GitLab (gathered from https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.com%2Fgitlab-org%2Fgitlab%2F-%2Fissues%2F121569%23note_1386895116&data=05|01||6bc86fc72f8a4521d5b908db5220407f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638194070686986155|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=WzoMPODmLZCURJ21%2BxoGUFwV%2FdoToIqlNF%2F1YGL02Nk%3D&reserved=0) but I can’t be certain.

The body of the e-mail that accompanied the forwarded original e-mail (so, what I added) however, was:

Error screenshot.


I expect your internal logs should be able to attribute something to that identifier?