Activate GitLab Enterprise Edition (EE) (PREMIUM SELF)

When you install a new GitLab instance without a license, only Free features are enabled. To enable more features in GitLab Enterprise Edition (EE), activate your instance with an activation code.

Activate GitLab EE

In GitLab Enterprise Edition 14.1 and later, you need an activation code to activate your instance.

Prerequisite:

• You must purchase a subscription.
• You must be running GitLab Enterprise Edition (EE).
• You must have GitLab 14.1 or later.
• Your instance must be connected to the internet.

To activate your instance with an activation code:

1. Copy the activation code, a 24-character alphanumeric string, from either:
   • Your subscription confirmation email.
   • The Customers Portal, on the Manage Purchases page.
2. Sign in to your GitLab self-managed instance.
3. On the left sidebar, select Search or go to.
4. Select Admin Area.
5. Select Subscription.
6. Paste the activation code in Activation code.
7. Read and accept the terms of service.
8. Select Activate.

The subscription is activated.

If you have an offline environment, activate GitLab EE with a license file or key instead.

If you have questions or need assistance activating your instance, contact GitLab Support.

When the license expires, some functionality is locked.

Verify your GitLab edition

To verify the edition, sign in to GitLab and select Help ({question-o}) > Help. The GitLab edition and version are listed at the top of the page.

If you are running GitLab Community Edition, you can upgrade your installation to GitLab EE. For more details, see Upgrading between editions. If you have questions or need assistance upgrading from GitLab Community Edition (CE) to EE, contact GitLab Support.

Troubleshooting

Cannot activate instance due to connectivity error

This error occurs when you use an activation code to activate your instance, but your instance is unable to connect to the GitLab servers.

You may have connectivity issues due to the following reasons:

• Firewall settings:

  • Confirm that GitLab instance can establish an encrypted connection to https://customers.gitlab.com on port 443. Note: IP addresses for https://customers.gitlab.com are 172.64.146.11 and 104.18.41.245)

  curl --verbose "https://customers.gitlab.com/"

  • If the curl command returns an error, either:
    • Configure a proxy in gitlab.rb to point to your server.
    • Contact your network administrator to make changes to an existing proxy or firewall.
  • If an SSL inspection appliance is used, you must add the appliance's root CA certificate to /etc/gitlab/trusted-certs on your instance, then run gitlab-ctl reconfigure.

• Customers Portal is not operational:

  • Check for any active disruptions to the Customers Portal on status.

• You have an offline environment:

  • If you are unable to configure your setup to allow connection to GitLab servers, contact your Sales Representative to request an Offline license.

    For assistance finding your sales representative you can contact GitLab support.