github-starred/newt
2
0
Fork 0
mirror of https://github.com/fosrl/newt.git synced 2026-03-08 23:03:03 -05:00
Code Issues 21 Packages Projects Releases 25 Wiki Activity

Access Resources with self signed TLS Certificate [Docker] #52

New Issue
Closed
opened 2025-11-19 07:12:54 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-19 07:12:54 -06:00
Owner
Copy Link

Originally created by @DevNinja90 on GitHub (Sep 1, 2025).

We have some resources that are only accessable via https. They automatically redirect thir webinterface via HTTP Status Code 307.
When running newt in debug mode this can be observed for the healthprobe.
A connection via pangolin is not succesfull.

We use pangolin in the cloud version for evaluation currently and newt in docker. 10.0.3.1 is the docker host and we want to access a web ui which the host runs. Unfortunately a filesystem / ssh access is not possible. TLS Certs could in theory be exchanged but this then needed to be done for every device (which we have 150 of) and they still would not be trusted.

> WARN: 2025/09/01 11:49:35 Target 1131: health check failed: Get "https://10.0.3.1/rpc": tls: failed to verify certificate: x509: certificate signed by unknown authority
> INFO: 2025/09/01 11:49:35 Target 1131 initial status: unhealthy

What could work:

  • Docker Wrapper Image which adds the CA of my custom devices and compiles again
  • A "allow self signed tls cert" flag i newt and in pangolin

Are there any plans for the secondary idea?

Originally created by @DevNinja90 on GitHub (Sep 1, 2025). We have some resources that are only accessable via https. They automatically redirect thir webinterface via HTTP Status Code 307. When running newt in debug mode this can be observed for the healthprobe. A connection via pangolin is not succesfull. We use pangolin in the cloud version for evaluation currently and newt in docker. 10.0.3.1 is the docker host and we want to access a web ui which the host runs. Unfortunately a filesystem / ssh access is not possible. TLS Certs could in theory be exchanged but this then needed to be done for every device (which we have 150 of) and they still would not be trusted. ``` > WARN: 2025/09/01 11:49:35 Target 1131: health check failed: Get "https://10.0.3.1/rpc": tls: failed to verify certificate: x509: certificate signed by unknown authority > INFO: 2025/09/01 11:49:35 Target 1131 initial status: unhealthy ``` What could work: - Docker Wrapper Image which adds the CA of my custom devices and compiles again - A "allow self signed tls cert" flag i newt and in pangolin Are there any plans for the secondary idea?
GiteaMirror commented 2025-11-19 07:12:55 -06:00
Author
Owner
Copy Link

@DevNinja90 commented on GitHub (Sep 1, 2025):

This isssue can be verified by making a wget command to the desired resource

@DevNinja90 commented on GitHub (Sep 1, 2025): This isssue can be verified by making a wget command to the desired resource
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
good first issue
help wanted
Improvement
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/newt#52
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?