Can't get winscp to copy files through socks5 server to destination host

I'm trying to copy a file using winscp from a windows client -> linux socks5 server -> linux host but am not sure what settings to put in the winscp program. I have tried various combinations but it doesn't work.

I'm using winscp 5.17
The socks server has port 8399 as the connection port.
In Winscp I select the socks5 protocol under advanced, connection, proxy.
1. What do I enter for a proxy host name? Should this be the external address of the socks server or localhost?
2. Should the port number be 8399 or 1089?
3. Do I need to setup firewall rules to allow the socks server to forward scp traffic directly to the linux host?

In new site SCP file protocol.
1. Is host name the linux host name?
2. Is the port number port 22, 1089, or 8399?
3. Is the user name the name of the linux account on the linux machine?
4. Do I need to setup firewall rules to allow traffic to go back through the socks server to the windows client?

ron101 wrote:

1. What do I enter for a proxy host name? Should this be the external address of the socks server or localhost?

The address of the SOCKS server..

2. Should the port number be 8399 or 1089?

You wrote that your SOCKS server has port 8399 – So that. I do not know what 1089 is.

3. Do I need to setup firewall rules to allow the socks server to forward scp traffic directly to the linux host?

Rules where? Your machine needs to have a network connectivity to the SOCKS server. And the SOCKS server needs network connectivity to the Linux host.

1. Is host name the linux host name?

Yes.

2. Is the port number port 22, 1089, or 8399?

Typically 22. Not the SOCKS port. Again, I do not know what 1089 is.

3. Is the user name the name of the linux account on the linux machine?

Yes.

4. Do I need to setup firewall rules to allow traffic to go back through the socks server to the windows client?

Incoming connection from the SOCKS server to the local machine is not needed.

martin wrote:

You wrote that your SOCKS server has port 8399 – So that. I do not know what 1089 is.

Thanks for the information Martin.
What do you recommend for a socks5 server on linux? I use shadowsocks which uses encryption. It doesn't seem like that will work with winscp then? Maybe I can disable encryption?
Port 1089 is the local port that the shadow socks client uses. I thought winscp could connect through the shadow socks client to the shadowsocks server using the local port? I initially tried winscp without going through the client but that failed so I tried other methods. Here is an example where they use port 1080 as the local port. https://www.linuxbabe.com/linux-server/setup-your-own-shadowsocks-server-on-debian-ubuntu-centos#:~:text=Setting%20Up%20Shadowsocks%20on%20Your%20Server&text=First%2C%20install%20python%20pip%20and,make%20encryption%20a%20little%20faster.&text=Create%20a%20configuration%20file%20with%20a%20command%20line%20text%20editor%20like%20nano%20.&text=Put%20the%20following%20text%20into%20the%20file.

3. Do I need to setup firewall rules to allow the socks server to forward scp traffic directly to the linux host?

Rules where? Your machine needs to have a network connectivity to the SOCKS server. And the SOCKS server needs network connectivity to the Linux host.

Since my attempts have failed I figured I needed a mechanism to get the scp traffic from the Socks5 host to the linux host?

Then I do not understand what is 8399.