Could not validate GitLab url

Hi,
I am new to SonarQube, and I have installed SonarQube v8.6 (developer version) on Docker (exported port 9000). I’m trying to connect to GitLab (On premise, version 12.0.1-ee), as described here
I am having problem in “Setting your global settings”. After creating a new configuration, I get this error:
sonarqube-error

Trying to add a new GitLab project, where I insert the GitLab access token manually, I get this error: `

Your personal access couldn’t be validated. Please make sure it has the right scope and that it is not expired.

The access token’s scopt is user_read (I also tried “api” and both “api” and “user_read”), and is valid.

In web.log, I see this error:

2021.01.17 09:21:51 ERROR web[AXcBf2MRWVqaqO8aAAbF][o.s.s.w.WebServiceEngine] Fail to process request http://xx.yy.zz.ww:9000/api/alm_integrations/check_pat?almSetting=SoftwareTest
java.lang.IllegalStateException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
.
.
.
Caused by: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

What can be its cause, and how can I fix it?

Thanks,
Amnon.

After carrying the steps described here I still have the same error, but the log states a different error:

Caused by: javax.net.ssl.SSLPeerUnverifiedException: Hostname XXXXXXXXX not verified:

My GitLab server has a self-signed certificate. I believe that this causes the problem.

Hi, yes indeed you have an SSL certificate issue. If you added it to the Keystore, it may be invalid or incomplete. Make sure you added the correct hostname to your certificate Server Name Indication extension.

Hi Pierre,

Thanks for your input. Yes, the names are the same.
I saw this issue, could missing SubjectAlternativeName in our self-signed certificate be the issue?

Amnon.

Yes, definitely.