General questions about Managed Service for GitLab
-
How can I migrate data from GitLab to Managed Service for GitLab?
-
Why cannot I push changes to my Managed Service for GitLab repository?
-
I get
500 Internal Server Errorwhen opening my instance. What could be the issue? -
How can I configure an alert for when disk usage reaches a certain percentage?
-
Can I change instance type or disk size after the instance has been created?
-
What should I do if I cannot connect to the system hook on
localhost?
What are the advantages of Managed Service for GitLab over a custom GitLab Community Edition installation?
The main advantage of Managed Service for GitLab is lower installation and administration costs for GitLab. In addition, Managed Service for GitLab adds features not found in Community Edition
How can I migrate data from GitLab to Managed Service for GitLab?
You can migrate data from a custom GitLab installation to Managed Service for GitLab. Learn how to do this in this guide. Before you begin, see how to run migration.
You cannot migrate data from GitLab.com to Managed Service for GitLab: migration is only available for GitLab installed on a server or local computer (self-managed GitLab).
Can I integrate GitLab authentication providers?
Yes, you can. To do this, configure OmniAuth.
Can I use Yandex ID or Yandex 360 for authentication?
Yes, you can. To do this, add a provider of the Yandex ID type to OmniAuth and configure its settings.
Is there GitLab integration with Yandex Tracker?
Yes, there is. For the integration settings, see Integration with Yandex Tracker
Why cannot I push changes to my Managed Service for GitLab repository?
Error messages:
You are not allowed to push code to this project.
You are not allowed to push code to protected branches on this project.
To push changes to a Managed Service for GitLab repository, assign
- To protected branches, e.g.,
master, assign theMaintainerorOwnerrole. - To unprotected branches, assign the
Developer,Maintainer, orOwnerrole.
Users with the Guest and Reporter roles cannot push changes.
For more information about roles, see the this GitLab article
I get 500 Internal Server Error when trying to open my instance. What could be the issue?
The instance may run out of disk space. You can increase the instance disk space on your own.
For details, see Cleaning up full instance disk space.
How can I clear pipeline logs to free up disk space?
Logs cannot be deleted separately. However, you delete them by deleting irrelevant pipelines.
Where can I monitor my disk space usage?
You can monitor your disk space usage:
- In the management console using the instance state monitoring tools.
- In Yandex Monitoring, where you also can set up alerts for specified metrics.
How can I configure an alert for when disk usage reaches a certain percentage?
See Setting up alerts in Monitoring for Managed Service for GitLab.
Why are backups not created?
If backup creation fails (the Failed status), set up a dedicated security group and assign it to the GitLab instance.
Can I change instance type or disk size after the instance has been created?
Yes, you can upgrade your instance to a higher-performance type and increase its disk size. However, you cannot reduce instance disk size or downgrade the instance to a lower-performance type. For more information, see Updating instance settings.
What should I do if I cannot connect to the system hook on localhost?
If you cannot connect to the system hook, use the 127.0.0.1 IP address instead of localhost:
- In the system hook settings (Admin area → System Hooks), change the URL value to
http://127.0.0.1:24080/default. - In the GitLab settings that allow sending messages to the local network (Admin area → Settings → Network → Expand outbound requests, the CIDR input field), add
http://127.0.0.1:24080to the list of IP addresses and domain names.