Closed Karbust closed 8 months ago
I am not sure what your issue is. The logs:
matching [teamcity.example.com] with [plex.example.com]
matching [teamcity.example.com] with [teamcity.example.com]
means: "an incoming connection wants to connect to teamcity.example.com. Is this the same as plex.example.com? No, I'll move to the next one. Is teamcity.example.com the same as teamcity.example.com? Yes. I'll connect there then". And I'd expect it connects to host: "192.168.1.161"; port: "6942".
You need to add what you're trying to do, what you're expecting, what you're getting and why is what you're getting not what you're expecting (although that part should be obvious).
I’m sorry, I thought it only logged the lines when it matched, not when it tried to match them.
Thank you for information.
Hello,
I'm having issues with connecting to an endpoint that sslh is configured to use.
It seems that it matches the same endpoint with multiple rules for some reason, making the application that matches
teamcity
to load, theplex
endpoint only matches the correct line. If I swap lines then it reverses,plex
starts matching both lines andteamcity
only matches the correct one.Output when I try to access
teamcity.example.com
:My config:
I'm running SSLH as a docker application on TrueNAS SCALE. The application is using a static IP. The container is running in priviledge mode with
CAP_NET_BIND_SERVICE
andCAP_NET_RAW
.