Has anyone gotten a Samba backend to work?

[ovizii]

I saved a Samba backend connection but round sync cannot open it. All the error messages I get is “unable to retrieve folder contents”.

All that the rclone log contains is:

2023/10/20 08:38:28 DEBUG : rclone: Version "1.63.1-extract" starting with parameters ["/data/app/~~rgdL1NU9RtNMyiiplZlRuQ==/de.felixnuesse.extract-UONZ1ia8nzmGEWWO7XWCQQ==/lib/arm64/librclone.so" "--config" "/data/user/0/de.felixnuesse.extract/files/rclone.conf" "--rc-addr" "localhost:38265" "--rc-user" "admin" "--rc-pass" "XevbP-aYBakh3QOgyTy4VQ==" "--rc-serve" "--log-file" "/storage/emulated/0/Android/data/de.felixnuesse.extract/files/logs/rcd.log" "--dump" "headers" "-vvv" "rcd"]
2023/10/20 08:38:28 INFO  : Using --user admin --pass XXXX as authenticated user
2023/10/20 08:38:28 NOTICE: Serving remote control on http://127.0.0.1:38265/
2023/10/20 08:40:17 INFO  : Signal received: terminated
2023/10/20 08:40:17 DEBUG : rclone: Version "1.63.1-extract" finishing with parameters ["/data/app/~~rgdL1NU9RtNMyiiplZlRuQ==/de.felixnuesse.extract-UONZ1ia8nzmGEWWO7XWCQQ==/lib/arm64/librclone.so" "--config" "/data/user/0/de.felixnuesse.extract/files/rclone.conf" "--rc-addr" "localhost:38265" "--rc-user" "admin" "--rc-pass" "XevbP-aYBakh3QOgyTy4VQ==" "--rc-serve" "--log-file" "/storage/emulated/0/Android/data/de.felixnuesse.extract/files/logs/rcd.log" "--dump" "headers" "-vvv" "rcd"]
2023/10/20 08:40:17 INFO  : Exiting...

I also exported the Samba config and looked into the zip file and the rclone config looked good. I am also able to connect to this Samba share with the exact same settings with another Android app called filesync so the credentials are good.

Any tips for me?

[newhinton]

Were you able to use your rclone config with your pc?

[ovizii]

I read your instructions to try that, but I didn't have a workstation to try it on available hence my question if it is known to work.

Will try to get around to try the rclone file from a desktop PC hopefully this weekend.

[ovizii]

I was just about to give it a try and connect via rclone from windows when I realized the rclone.conf file has no field for the share name - where would I pass that through? I mean I am trying to access a specific share on a given server.

Any hints? The rclone docu doesn't really help or am I missing something here?
https://rclone.org/smb/ says Paths are specified as remote:sharename

the rclone.conf file which I exported from round sync contains:

[android-backups]
type = smb
port = 445
pass = redactedPassword
host = 100.xxx.xxx.xxx
user = android-backups 

I tried an ls command via rclone:
.\rclone ls android-backups:/android-backups

but I simply get this error:

2023/10/23 16:09:32 ERROR : : error listing: couldn't connect SMB: response error: The attempted logon is invalid. This is either due to a bad username or authentication information.
2023/10/23 16:09:32 Failed to ls with 2 errors: last error was: couldn't connect SMB: response error: The attempted logon is invalid. This is either due to a bad username or authentication information.

[newhinton]

[android-backups] is your shares name.

So the command you are using is correct, as is the error.

How did you add pass to your config? Did you manually enter it?

[ovizii]

[android-backups] is your shares name.

So the command you are using is correct, as is the error.

Thanks for helping me figure this out. So in this case, the name of the rclone remote is android-backups and the name of the samba share is also the same as is the user name to accessing the samba share

How did you add pass to your config? Did you manually enter it?

I entered the password in the round sync GUI when I created the rclone remote. I entered it in the field named "pass" - when I exported the config it was inside rclone.conf

I did some more tests, I think I had an extra "/" in my command above so I tried these too. I reread the rclone cos and the right syntax would be: remote:sharename (no / before the sharename).

.\rclone lsd android-backups:
and
.\rclone ls android-backups:android-backups

While testing in reverse, I can not access any samba share via rclone on my desktop no matter what share or user/passsword combo I try. I never used rclone from my desktop, this is the first time.

Anyway, could you maybe share a snippet of your rclone.conf while masking the password, so I can compare if I have got something wrong?
Does accessing a samba share via round sync work for anyone else?

[newhinton]

[nas]
type = smb
host = 192.168.1.86
pass = XXXX

This is a modified version of the entry rclone (on pc) created for me for smb. It works quite flawless for me.
Though now you ask, i wonder why it works since i dont have supplied a user, and i am not sure my system user is the same one my nas accepts. Anyway.

Just to make sure that it does not pose a problem, can you please remove the port setting?

Though you really should check if your username and password combination works, because the error you posted is quite clear...

[ovizii]

• I removed the port and it didn't make any difference, still the same error
• the credentials work, as I have tested them with another android app called foldersync
• I must be doing something really wrong as I cannot use rclone from my Windows machine at all to connect to any SMB share with any credentials.
• If I connect with foldersync using SMB1/2/3 I always see an entry in the logs of my samba server while when trying to connect with round sync I never see any log entry, just the fail from round sync itself

I thought I had figured out the problem. I tested these credentials again with the other app called foldersync and saw I can choose the SMB version. The credentials failed with SMB1 only SMB 2 and SMB 3 worked which leads me to the conclusion that rclone uses SMB1.

Unfortunately this still does not seem to be the solution as rclone states here: https://rclone.org/smb/ that it uses the go-smb2 library https://github.com/hirochachacha/go-smb2/ which calls itself "SMB2/3 client library written in Go."

I have no clue what is going on. I will wait a few days, think it through again and continue the discussion here if I have any other idea.

[TalalMash]

Fresh remote, on latest version.
Export:

[smbtest]
type = smb
rclone_remote_name = smbtesy
pass = driTjBClkqTbggRjh_mJHzXPZa4fQw
host = 192.168.1.171
user = user

Pass: linwin

[ovizii]

OK, so on your install it encrypts the PW and does not save it in cleartext which explains why it works.

[newhinton]

@ovizii Can you confirm that your password is longer than 21 characters, also for your sftp-test?

[ovizii]

I use a password manager and the current length it is set to is 32 characters long. I double-checked both passwords, and they are indeed 32 characters long.

[ovizii]

Just to make sure we're on the same page:

I use RS 2.2.2 and I just created a new SMB backend, typed a 32 character long password, exported the config, opened the zip file, opened rclone.conf and the line: pass = contained my cleartext password I just typed.

[ovizii]

I managed to get rclone working from my windows machine.

 .\rclone.exe ls android-backups:android-backups
     7352 docker-compose.yml

I did a rclone config then chose to edit my android-backups remote, entered the very same values again and checked the resulting rclone.conf file.

THE DIFFERENCE is that the password was encrypted when rclone stored it.
When exporting from round sync after opening the zip file, the included rclone.conf shows the password in clear text. I guess I could copy the encrypted password back into this zip file and import it in round sync but this seems really stupid to me.

Any feedback is very much appreciated.

[newhinton]

Huh, i need to check if rclone changed, this is not the first issue of this kind, albeit i didnt make the connection

[newhinton]

Quick question, do you run 2.2.2?

[ovizii]

yes, 2.2.2 installed via obtainium directly from your GitHub page.

[ovizii]

I tried an SFTP remote just for the fun of it and faced the same issue that round sync saves the password in clear-text while rclone on my desktop saves it in some hashed form so even with SFTP I had to configure the remote on the desktop and then import the config on my phone for it to work.

[newhinton]

You could try v2.4.3-beta, that should have fixed it

[ovizii]

I updated to 2.4.3-beta-debug and deleted my working remotes which I had created on my desktop and imported into RS. I then manually recreated them via RS, saved them, exported the config and found that the password was indeed obfuscated.
I still could not connect with the config written by RS.
I then reimported the above-mentioned working configs and all is working again.

Not sure what is wrong here but it's definitely not the credentials as I use a password manager so no typos happened.