[GH-ISSUE #124] configuration error: tls invalid protocol "sni" #73

Open
opened 2026-05-05 10:59:42 -06:00 by gitea-mirror · 6 comments
Owner

Originally created by @Abdo-Saleh on GitHub (Jan 25, 2021).
Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/124

tunnel.ymal file:

server_addr: 64.x.x.x:5223
tunnels:
webui:
proto: http
addr: localhost:4200
host: chatbot.x.online
tls:
proto: sni
addr: localhost:8000
host: developer.x.online

x was filled with my public server ip or its name, and it's hidden here.

when I am trying to connect, the following error is appearing
configuration error: tls invalid protocol "sni"

Originally created by @Abdo-Saleh on GitHub (Jan 25, 2021). Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/124 tunnel.ymal file: server_addr: 64.x.x.x:5223 tunnels: webui: proto: http addr: localhost:4200 host: chatbot.x.online tls: proto: sni addr: localhost:8000 host: developer.x.online _x was filled with my public server ip or its name, and it's hidden here._ when I am trying to connect, the following error is appearing **configuration error: tls invalid protocol "sni"**
Author
Owner

@synaption commented on GitHub (Feb 16, 2021):

I'm having the same issue

<!-- gh-comment-id:780047264 --> @synaption commented on GitHub (Feb 16, 2021): I'm having the same issue
Author
Owner

@synaption commented on GitHub (Feb 20, 2021):

I just deleted the tls part of the config file. I think the error might have something to do with having a valid CNAME? I don't know a lot about that sort of thing, but it works for me now.

<!-- gh-comment-id:782744258 --> @synaption commented on GitHub (Feb 20, 2021): I just deleted the tls part of the config file. I think the error might have something to do with having a valid CNAME? I don't know a lot about that sort of thing, but it works for me now.
Author
Owner

@Abdo-Saleh commented on GitHub (Feb 23, 2021):

i did remove that part and it works, but i needed it actually

<!-- gh-comment-id:784558123 --> @Abdo-Saleh commented on GitHub (Feb 23, 2021): i did remove that part and it works, but i needed it actually
Author
Owner

@giper45 commented on GitHub (Mar 24, 2022):

Hello, any news about it?

<!-- gh-comment-id:1077975777 --> @giper45 commented on GitHub (Mar 24, 2022): Hello, any news about it?
Author
Owner

@giper45 commented on GitHub (Mar 24, 2022):

Think that it is not more release.
Commit:
f48a09d2ab

should have added sni support.
Issue #115 should be related.
I try to build the master version to verify if it is supported.

<!-- gh-comment-id:1077984470 --> @giper45 commented on GitHub (Mar 24, 2022): Think that it is not more release. Commit: https://github.com/mmatczuk/go-http-tunnel/commit/f48a09d2ab15c6f4fcbeec67864d39a584f22b30 should have added sni support. Issue #115 should be related. I try to build the master version to verify if it is supported.
Author
Owner

@giper45 commented on GitHub (Mar 24, 2022):

Confirmed that when building master version (tunnel and tunneld), the sni is enabled.

<!-- gh-comment-id:1078020118 --> @giper45 commented on GitHub (Mar 24, 2022): Confirmed that when building master version (tunnel and tunneld), the sni is enabled.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/go-http-tunnel#73
No description provided.