You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first connection just hangs (e.g. wget --spider -q http://localhost:8080). While all is running, coming from an outside host (somewhere around the world), it gets an immediate reply, but also 'unhangs' the first one.
Doing it the other way around, connecting from around the world, the connection hangs. Connecting internally, also hangs, but it unblocks the external connection which now gets a reply. The internal one this time, sits there trying, until the external is up again, which then unblocks the internal one. This both 8080, but also 443.
So in short;
localhost -> external: hang, but release
external -> localhost: hang, hang, release
btw, only external host can connect over any (configured) port to unhang the internal connection. Probably some firewall rule shenanigans, where the external access triggers a 'new,established' thing ...
The text was updated successfully, but these errors were encountered:
When start sslh, and having a configuration such as:
The first connection just hangs (e.g.
wget --spider -q http://localhost:8080
). While all is running, coming from an outside host (somewhere around the world), it gets an immediate reply, but also 'unhangs' the first one.Doing it the other way around, connecting from around the world, the connection hangs. Connecting internally, also hangs, but it unblocks the external connection which now gets a reply. The internal one this time, sits there trying, until the external is up again, which then unblocks the internal one. This both 8080, but also 443.
So in short;
localhost -> external: hang, but release
external -> localhost: hang, hang, release
btw, only external host can connect over any (configured) port to unhang the internal connection. Probably some firewall rule shenanigans, where the external access triggers a 'new,established' thing ...
The text was updated successfully, but these errors were encountered: