sshfs-win-manager icon indicating copy to clipboard operation
sshfs-win-manager copied to clipboard

connection fails, but spinning icon goes forever

Open Goddard opened this issue 1 year ago • 7 comments

So I had a local ip change to a ssh server I usually mount. It isn't a huge deal I can usually just go in and change it. I am unable to do that now though as the spinning icon just continues forever. Hitting edit mode or delete mode does nothing. Closing the manager and re-opening doesn't help.

On Windows 11 and using 1.31

Goddard avatar Apr 16 '23 05:04 Goddard

same here on Windows 10

sknull avatar Apr 16 '23 14:04 sknull

Can confirm this on Win 11 also. For me it only happens if I have connect on startup enabled. And I have 3 different mount points and two of them usually just keep "endlessly" loading even though I can access them fine. kuva

ghost avatar May 14 '23 08:05 ghost

I am having this issue as well. However, as a work around until it gets fixed, you can delete the %appdata%\SSHFS-Win Manager folder. It clears everything.

shave999 avatar Jul 23 '23 23:07 shave999

I am having this issue as well. However, as a work around until it gets fixed, you can delete the %appdata%\SSHFS-Win Manager folder. It clears everything.

image Not so good at programming, it has two errors, %appdata%/ it has two folders in uppercase and lowercase letters so the config is not loaded correctly.

It still loads even though I deleted the whole config.

kkm avatar Nov 13 '23 20:11 kkm

I am having this issue as well. However, as a work around until it gets fixed, you can delete the %appdata%\SSHFS-Win Manager folder. It clears everything.

Did not resolve the issue for me.

johnrclark3 avatar Jan 03 '24 17:01 johnrclark3

A workaround for me was to, exit sshfs-win manager, then modify %appdata%\Roaming\sshfs-win-manager\vuex.json for each connection that may have the problem it likely has status key set to connecting, which i changed to disconnected then start sshfs-win manager again

There are possibilities where it may not connect due to conflicting mount points, say a removable usb drive that has been connected that took over the letter, or a network drive that used the same drive letter.

	"state": {
		"Data": {
			"connections": [
				{
					"advanced": {
						"connectOnStartup": false,
						"customCmdlOptions": [],
						"customCmdlOptionsEnabled": false,
						"reconnect": true
					},
                                       ...
					"status": "connecting",  
				},
...

changed to

	"state": {
		"Data": {
			"connections": [
				{
					"advanced": {
						"connectOnStartup": false,
						"customCmdlOptions": [],
						"customCmdlOptionsEnabled": false,
						"reconnect": true
					},
                                       ...
					"status": "disconnected",  
				},
...

JCBuck avatar Jan 15 '24 07:01 JCBuck