Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CedarDevs Unable_To_Verify_Leaf_Signature certificate error #1505

Open
uniyalVJ opened this issue Apr 12, 2021 · 1 comment
Open

CedarDevs Unable_To_Verify_Leaf_Signature certificate error #1505

uniyalVJ opened this issue Apr 12, 2021 · 1 comment
Assignees

Comments

@uniyalVJ
Copy link
Collaborator

uniyalVJ commented Apr 12, 2021

Bug Description
Upon booting up sitemap pod it is unable to connect to the cedardevs API URL:
This seems to be not strictly related to sitemap and a long time existing bug regarding cedardevs

https://cedardevs.org/onestop/api/search/search/collection/

Platform/Environment
Mac OS

Severity
Severity: HIGH (High/Medium/Low)
Priority: MEDIUM (High/Medium/Low)

To Reproduce
Steps to reproduce the behavior:

  1. Branch 726-sitemap-review-cron
  2. Run skaffold with sitemap profile
  3. After search pod is up and running, sitemap pod will crash and output logs on skaffold showing UNABLE_TO_VERIFY_LEAF_SIGNATURE

Expected Result
Connects to cedardevs API & runs sitemap script properly to generate sitemap files.

Actual Result
See screenshots.

Screenshots
If applicable, add screenshots to help explain your problem.

image.png

image.png

Additional context
Add any other context about the problem here.

@uniyalVJ uniyalVJ self-assigned this Apr 12, 2021
@uniyalVJ uniyalVJ changed the title Sitemap Unable_To_Verify_Leaf_Signature certificate error CedarDevs Unable_To_Verify_Leaf_Signature certificate error Apr 12, 2021
@uniyalVJ
Copy link
Collaborator Author

uniyalVJ commented Apr 12, 2021

In order to narrow down the scope of the issue I implemented by setting the environment variable inside of my CLI

process.env['NODE_TLS_REJECT_UNAUTHORIZED'] = 0

This disables Node from rejecting self-signed certificates by allowing ANY unauthorized certificate. Although it is an insecure approach if it worked it would show that it is directly a certificate issue. It didn't work meaning that this is not a simple problem of having the correct certificates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant