Ray was unable to bind to the remote server's port (on Siteground)

[web-elements]

Describe the bug
When I try to connect to any Siteground server using ssh key
"Ray was unable to bind to the remote server's port.
Is the port in use or is someone else using ray on this server?"
But I can connect correctly through terminal on mac.
I have seen #685 and https://unix.stackexchange.com/questions/427189/how-to-cleanup-ssh-reverse-tunnel-socket-after-connection-closed
but I don't have permission to do this thinks on a siteground server.

Versions
Ray version (you can see this in "About Ray"): 2.4.0

To Reproduce
Steps to reproduce the behavior:

1. add a siteground server
2. insert the data in the form (the same that I use in the terminal where is working)
3. try to connect to the server
4. See error

Expected behavior
It should connect to server.

Desktop (please complete the following information):

• OS: macOS
• Version 12.6

Additional context
I haven't had any problems with other servers, only with those of Siteground

[jkbennemann]

I do have the same issue with other hosters as well, not just siteground.
I think this could be related to some kind of version incompatibilites.

The servers I tested run on

• OpenSSH v.8.9p1
• OpenSSL 3.0.2

[colinr-l]

I have the same problem as other posters when trying to connect Ray to a Wordpress site on a remote server at Siteground.
I am using Windows and am able to connect to remote server via ssh on Windows Powershell but get "Ray was unable to bind to the remote server's port" when trying to connect using Ray:

[menshinobi]

Any solution to this issue?

[lansezzz]

Any solution to this issue?

[federicociti]

Any solution to this issue?

[colinr-l]

No, unfortunately not, I reverted to manual coding debug statements. From: federicociti ***@***.***> Sent: Wednesday, April 3, 2024 3:30 PM To: spatie/ray ***@***.***> Cc: colinr-l ***@***.***>; Comment ***@***.***> Subject: Re: [spatie/ray] Ray was unable to bind to the remote server's port (on Siteground) (Discussion #808) Any solution to this issue? — Reply to this email directly, view it on GitHub <#808 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXPYXFOT7TZ6NLPNFLOSBHLY3QG63AVCNFSM6AAAAABB4P77M6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSOJXHE4DG> . You are receiving this because you commented.Message ID: ***@***.***>