What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

GitLab Build Status Sensor Fails Upon Creation

Votes:

0

Hello,

I am attempting to create a GitLab Build Status Sensor for our cloud deployment of GitLab. Upon creating the sensor, you are asked for your access token. Hovering over the `i`, a toast appears that states the access token can be generated via your GitLab profile settings (thus this is not a group or project level access token or webhook).

When I generate an access token for my user (w/ owner permission level), and paste it in the dialog box, I get the following error:

Could not create the GitLab Build Status BETA sensor on device Gitlab (gitlab.com).

Failed to establish secure connection [Step 0] Error connecting with SSL. Error connecting with SSL. error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure [Step 1] Error connecting with SSL. Error connecting with SSL. error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol [Step 2] Error connecting with SSL. Error connecting with SSL. error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure [Step 3] Error connecting with SSL. Error connecting with SSL. error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure [Step 4] Error connecting with SSL. Error connecting with SSL. error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number [Step 5] Error connecting with SSL. Error connecting with SSL. error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol [Unsecure] IOHandler value is not valid

The manual page for the GitLab Build Status sensor does not provide a lot of detail, and I cannot find much information in the community to help troubleshoot this issue. As our GitLab instance is a cloud deployment, our device's service URL is https://gitlab.com, and the IPv4/ DNS name is set as gitlab.com. Am I configuring the sensor correctly, or am I missing something?

beta gitlab prtg sensor

Created on Oct 12, 2020 4:28:10 PM



1 Reply

Votes:

0

Hi there,

Thank you for your message.

According to the error message, it seems you're not able to contact the target server. Could you please add a HTTP sensor on that device - is this sensor working?

Kind regards,
Andreas Günther
Tech Support, Paessler AG

[email protected]

Created on Oct 13, 2020 2:08:18 PM by Andreas Günther [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.