doc/subscriptions/gitlab_com/gitlab_subscription_troubleshooting.md
{{< details >}}
{{< /details >}}
When you purchase or use subscriptions for GitLab, you might encounter the following issues.
When you purchase a GitLab subscription, your credit card might be declined because:
Check with your financial institution to confirm if any of these reasons apply. If they don't apply, contact GitLab Support.
transaction_not_allowedWhen you purchase a GitLab subscription, you might get an error that states:
Transaction declined.402 - [card_error/card_declined/transaction_not_allowed]
Your card does not support this type of purchase.
This error indicates that the type of transaction you are making is restricted by your card issuer. It is a security measure designed to protect your account.
Your transaction might be declined because of one or more of the following reasons:
To resolve this issue, try the following:
Attempt_Exceed_LimitationWhen you purchase a GitLab subscription, you might get the error
Attempt_Exceed_Limitation - Attempt exceed the limitation, refresh page to try again..
This issue occurs when the credit card form is re-submitted three times within one minute or six times within one hour. To resolve this issue, wait a few minutes and retry the purchase.
Subscription not allowed to addWhen you purchase subscription add-ons (such as additional seats, compute minutes, storage, or GitLab Duo Pro)
you might get the error Subscription not allowed to add....
This issue occurs when you have an active subscription that:
To resolve this issue, contact your GitLab sales representative to assist you with the purchase.
To view purchases in the Customers Portal on the Subscriptions & purchases page, you must be added as a contact in your organization for the subscription.
To be added as a contact, create a ticket with the GitLab Support team.
On GitLab.com, if you cannot link a subscription to your namespace, you might have insufficient permissions. Ensure that you have the Owner role for that namespace, and review the transfer restrictions.
On GitLab Self-Managed or GitLab Dedicated, your subscription data might fail to synchronize. This issue can occur when network traffic between your GitLab instance and certain IP addresses is not allowed.
To resolve this issue, allow network traffic from your GitLab instance to the IP addresses
172.64.146.11:443 and 104.18.41.245:443 (customers.gitlab.com).
For more information, see troubleshooting connectivity issues.