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.

Sign up for GitHub

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

Jump to bottom

Gateway TLS passthrough blocking other GWs #152

Open
sebiklamar opened this issue Jan 5, 2025 · 1 comment
Open

Gateway TLS passthrough blocking other GWs #152

sebiklamar opened this issue Jan 5, 2025 · 1 comment
Assignees
@sebiklamar
Labels
help wanted Extra attention is needed

Comments

@sebiklamar
Copy link
Collaborator

With implementation of TLS passthrough GW (tls-passthrough) in 62f9dca other ingress GWs got unavailble. E.g. whoami and unifi were accessible, though SSL connection could get established somehow.
WIth disabling tls-passthrough GW access to whoami and unifi (and ubble and cmk) apps got possible
@sebiklamar sebiklamar self-assigned this Jan 5, 2025
@sebiklamar sebiklamar converted this from a draft issue Jan 5, 2025
@sebiklamar sebiklamar added the help wanted Extra attention is needed label Jan 5, 2025
sebiklamar added a commit that referenced this issue Jan 5, 2025
@sebiklamar
fix(gateway): disabling tls-passthrough GW as workaround for #152
145e5c7 
... b/c other GWs were not accessible
@sebiklamar
Copy link
Collaborator Author

disabling tls-passthrough GW in 145e5c7 as workaround b/c other GWs were not accessible

sebiklamar added a commit that referenced this issue Jan 8, 2025
@sebiklamar
fix(unifi): deleting tls-route as it's not working (#122, #152)
e9158e0 
see also #122 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sebiklamar sebiklamar

Labels
help wanted Extra attention is needed
Projects
homelab project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sebiklamar