Fix https across lab tunnel #537

Closed
opened 2024-11-29 00:12:03 +00:00 by SeanOMik · 1 comment
Owner

For some reason, the lab cannot connect to the ingress on the thin client cluster through https across the wireguard tunnel. Http works fine, but https does not. I'm not sure how to debug this.

For some reason, the lab cannot connect to the ingress on the thin client cluster through https across the wireguard tunnel. Http works fine, but https does not. I'm not sure how to debug this.
Author
Owner

This was fixed by using 8443 instead of 443 for the external ingress and changing the traefik dynamic config on the docker vm to proxy to it. No clue why 443 wasn't working, it must have been blocked by something, but idk what. At least this works.

This was fixed by using 8443 instead of 443 for the external ingress and changing the traefik dynamic config on the docker vm to proxy to it. No clue why 443 wasn't working, it must have been blocked by something, but idk what. At least this works.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: SeanOMik/k3s-cluster#537
No description provided.