SSL errors when configuring a private repository in Liferay PaaS
Written By
Giulianna Munoa
How To articles are not official guidelines or officially
supporteddocumentation. They are community-contributed content and may
not alwaysreflect the latest updates to Liferay DXP. We welcome your
feedback toimprove How to articles!
While we make every effort to ensure this Knowledge Base is accurate,
itmay not always reflect the most recent updates or official
guidelines.We appreciate your understanding and encourage you to reach
out with anyfeedback or concerns.
Legacy Article
You are viewing an article from our legacy
"FastTrack"publication program, made available for
informational purposes. Articlesin this program were published without a
requirement for independentediting or verification and are provided
"as is" withoutguarantee.
Before using any information from this article, independently verify
itssuitability for your situation and project.
Issue
- You are using a private repository and while trying to configure it for the CI service you notice the webhook is not automatically created
- Also the following logs are shown in the INFRA environment
Aug 13 16:11:14.665 build-6 ci[ci-0] [DXP Cloud] The value set for LCP_CI_SHALLOW_CLONE_DEPTH is invalid:
Aug 13 16:11:14.665 build-6 ci[ci-0] [DXP Cloud] Value must be an integer.
Aug 13 16:11:16.070 build-6 ci[ci-0] [WARNING][io.jenkins.plugins.gitlabbranchsource.GitLabHookCreator register] Could not manage project hooks for user/liferay-dxp-cloud on https://gitlab.privateserver.com/
Aug 13 16:11:16.070 build-6 ci[ci-0] org.gitlab4j.api.GitLabApiException: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at org.gitlab4j.api.AbstractApi.handle(AbstractApi.java:664)
at org.gitlab4j.api.AbstractApi.get(AbstractApi.java:216)
at org.gitlab4j.api.Pager.(Pager.java:92)
....
Resolution
- This is caused by SSL validation errors with the certificate from the private server, likely, the certificate installed is not trusted by all browsers.
- You can check if the certificate is valid using third-party tools such as SSL Checker
- Once the certificate chain is correct, you can try saving the environment variables in the CI service again and check if this automatically creates the webhook in your repository.
Did this article resolve your issue ?