Bug: SSH Tunnels that fail to open are noted with incorrect error message

[expired user #6960]'s profile image [expired user #6960] posted 11 years ago in Feature discussion Permalink
When setting up multiple SSH Tunnels, the user must specify the port(s) to use when using those tunnels completely manually. There is no error message thrown when the local port cannot be opened, resulting in the only error being an "Access denied" message.

The correct error message to display would be that the tunnel failed for some reason, and not give a generic "Access denied" message.

Alternatively, we could check for the port status before the tunnel connection is attempted, and report an error if the port is busy.
ansgar's profile image ansgar posted 11 years ago Permalink
Then, why do you get an "Access denied" - is it a local MySQL server returning that error?
ansgar's profile image ansgar posted 11 years ago Permalink
However, how do I check whether a port is already in use?
jfalch's profile image jfalch posted 11 years ago Permalink
cf this.
ansgar's profile image ansgar posted 11 years ago Permalink
Thanks. As I already use Synapse, that noted Synapse approach should be right and elegant.

Please login to leave a reply, or register at first.