Troubleshooting GitLab on-premise connection

Trying to create a pipeline from a repo on a self-managed on-premises GitLab server. The repo server only allows connections from whitelisted IPs, so I have whitelisted the cloud.seqera.io IPs that are returned from https://meta.seqera.io (“18.135.7.45/32”, “18.169.21.18/32”, and “18.171.4.252/32”). I’ve also created a GitLab credential in Seqera with my PAT (have confirmed it works outside Seqera) and the URL of the GitLab server as the repository base URL.

When I create a pipeline and put in the repository URL (HTTPS, not SSH) I get “Unexpected error while processing request” along with some kind of error ID. This error is not descriptive at all and provides no information on why Seqera was unable to connect to by GitLab server. Is there some way I can get more details on the error?

I work with Jared. Checking in with Seqera on how we can troubleshoot? This is for a paying customer.

The best way to get a response from the support team is to raise a support request, it will include many of the respondents here but be covered by our SLAs.

From this problem, the backend logs should include the error returned when Seqera Platform tried to reach out to the Gitlab server. You can search the logs by the error ID you see in the platform to extract the exact error message.

Thanks! Do you have instructions for opening a case. We do not see the option from the Seqera console?

For the logs this issue is not with a pipeline. It errors out when setting up the Gitlab credential. How do we see Seqera level (non pipeline logs)?

The support portal is located here: https://support.seqera.io/ You should have been given an account after onboarding. Send us an email

As for the logs, they are produced by the backend service itself. You will need access to the backend service, which will depend on your deployment. When you add the credentials the error will appear there.