SFTP connection takes 30-90 seconds to establish with GNOME Nautilus

[Xgabi86]

Current Behavior

When connecting to a server via SFTP using GNOME Nautilus 50.2.2 (sftp://node.example.com:2022), the connection takes between 30 and 90 seconds to fully establish before the file browser becomes usable. This happens consistently on every server managed by the panel.
No errors are logged on the Wings side during the delay, the connection eventually succeeds.

Expected Behavior

The SFTP connection should establish in under a few seconds, comparable to a direct SSH connection to the host machine (~1 second).

Steps to Reproduce

1. Open GNOME Nautilus (Files) 50.2.2
2. Go to Network tab
3. Enter sftp://<user>@<node-host>:<sftp-port> (e.g. sftp://example@example.com:2022)
4. Enter credentials when prompted
5. Observe the connection taking 30-90 seconds before the file listing appears

Panel Version

1.0.0-beta33

Wings Version

v1.0.0-beta24

Games and/or Eggs Affected

All servers / all eggs (issue is not game-specific)

Docker Image

Affects all images

Error Logs

Wings: https://logs.pelican.dev/abd664c3
Panel: https://logs.pelican.dev/00c5fc86

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.
• I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
• I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.

[notAreYouScared]

I honestly don't think this is a wings issue... I don't think anyone on the team runs linux to try it.

[Xgabi86]

I've tried this on several distros, and therefore with different versions of Nautilus, and I've always had this problem.
Maybe Nautilus tries to connect via SSH and then switches to SFTP?

[NerdsCorp]

It not a wings issue, it also does it with the KDE file manager dolphin, use FileZilla and it will work fine.

[phatblinkie]

sounds more like the server your sftp'ing to is looking reverse dns and failing before it lets you . check your ssh and logging settings on the host running wings

in your wings host /etc/ssh/sshd_config make sure
UseDNS no
GSSAPIAuthentication no

restart sshd with systemctl restart sshd and try that. happens to apache too if reverse dns is being required for its logging, and it has either a bad dns server set, or the reverse for the client ip just doesnt exist. symtom is exactly the same though, no responses until the dns checking times out