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

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.

Then, why do you get an "Access denied" - is it a local MySQL server returning that error?

However, how do I check whether a port is already in use?

cf this.

Thanks. As I already use Synapse, that noted Synapse approach should be right and elegant.