This guide for troubleshooting for error on CustomersDot.
When purchasing a subscription via the CustomersDot if a user receives an error
about an address or credit card, check the address listed in the
section of the CustomersDot. This is typically due to a bad address
(city/state/zip code). If the address is correct and the error persists, check
Sentry for a relevant error and file an issue in the
CustomersDot tracker as necessary.
To find the error specifically related to a customer on sentry, try the following:
Customerssearch page by clicking on
Customerson the left panel
customerIDwith the actual customerID from CustomersDot)
Sometimes a customer reports that they did not receive an email from the portal, such as a password reset request or new account confirmation. GitLab uses Mailgun as a service to send outgoing mail. We can login to Mailgun to view the message logs, and when appropriate, remove suppressions.
The general workflow that Support uses for this process is documented in the Support handbook page on confirmation emails, and that page has a full description on navigating the Mailgun dashboard and searching through the logs.
The process here is much the same, but since we are investigating mail from CustomerDot, in Step 4 of the general workflow ensure that
customers.gitlab.com is selected as the domain to search under.
Note that reseller customers will not have access to customers.gitlab.com and subsequently, password reset emails will not be sent to them. Check whether the customer has access to customers.gitlab.com by navigating to the
Edit page for the customer record (pen icon on right-side of customer record) and looking at the
Login activated checkbox. If the checkbox is ticked, the customer has access; if the checkbox is not ticked, the customer will not have access and they will not receive password reset emails. Reseller customers should make their purchases via our Sales team.