Waseh

In commandline, first: pgrep -f "rclone.*--rc-web-gui" Which gives you a number (the PID) then kill -SIGINT (insert number from above command here but with no parenthesis)

Likely because you already have one running. You would have to kill any other instance running on the same port.

Just pushed a new update that should fix the WebUI problem.

I didn't realize there was a problem with the webui. It seems the webui is spawning under the rclone binary that limetech has included with 7.2+. So a webui is actually spawning when you enable it in the plugin (try opening your.ip:5572), though it (probably) wont have your config. I'll investigate if it's easily fixable, and if not i might just disable it in the plugin until i or someone else has time to debug it.

Hi guys Just a quick announcement - I finally got to upgrading to 7.2.0 and have just pushed an update to the plugin that should fix the version number error introduced in the latest versions of unraid. As i understand it the deprecation warning Squid had put in CA has already been removed, so the plugin should be back in fully working order and available in CA. Cheers

I haven't upgraded yet. If rclone ships with 7.2+ this would seem to be the most prudent way forward. How are updates handled for the rclone binary? Is it reliant on new unRAID versions or updated independently? Anyways I haven't upgraded to 7.2 yet and won't for another month or so. I won't be updating the plugin if the native solution is sufficient for users of the plugin.

https://rclone.org/remote_setup/

Did you ever solve this? I just upgraded some hardware and also added a 2.5g intel NIC to avoid new onboard realtek but have the same issue. Used to run a 10g SFP+ NIC but wanted to go back to ethernet for convenience. Ended up not being convenient at all 😅

Have you tried the good old reboot? 😅

What happens if you run which unzip

First step would be to try and unzip it and getting the binary into the correct path: unzip -o -j "/boot/config/plugins/rclone/install/rclone.zip" "*/rclone" -d "/boot/config/plugins/rclone/install" cp /boot/config/plugins/rclone/install/rclone /usr/sbin/rcloneorig chown root:root /usr/sbin/rcloneorig chmod 755 /usr/sbin/rcloneorig Try running these sequentially and see if any of them fails.

@Mikeve97 That's odd. Could you try running curl --connect-timeout 15 --retry 3 --retry-delay 2 --retry-max-time 30 -o /boot/config/plugins/rclone/install/rclone.zip --create-dirs https://downloads.rclone.org/rclone-current-linux-amd64.zip And see what the output is? Most likely either the download or the unzip is failing somehow.

@adoucette Without anymore debugging info it's hard to say why it's not working for you. Just tested updating (and changing branches from stable to beta and back to stable) on my end and that still works as well (on the newest version of unraid). This just to say that the plugin is still working. Your post indicates that it does not, and while that may be the case for you, it is not the true in general

@adoucette - Still working for me. However I'm not even sure what you mean by " I don't need to use the full docker". This plugin has no docker container involved at all? And can also update the rclone version. Are you sure this is the correct thread for the plugin/docker container you're talking about?

Beta support seems to have been added to the rclone beta branch a couple of months ago, so just go to the settings page for the plugin and change to the beta branch? No need for an update.

I haven't gotten the message yet but decided to take migrate everything to my own storage again. Didn't really use much more storage in the cloud than i have local anyway so it was more of a backup than anything. Just have to find a new offsite backup solution for non-replacable data. I think the (almost) free ride from Google is finally comming to an end.

If anybody else who has this problem can confirm it as a fix I'm happy to implement it for everybody

In the logs you posted it already starts by throwing errors trying to copy the existing rclone binary to the sbin directory. Then you get errors trying to just download the untouched zip file from the rclone webpage to your flash drive and then errors trying to create a config file. If anything it's the rclone folder it doesn't like. I suggest reading up on IO errors and see if you can find a solution that way.

You're having I/O errors on your flash drive. I'd be surprised if this was related to the rclone plugin. Could be a corrupt filesystem or dying flash drive or any other number of things. But again I don't think this is related to this plugin specifically.

That's why the error asks to check firewall and DNS settings 😉 seems you have some sort of connectivity problem. I'll try and make the error message a bit more helpful in the future

@micci Can you successfully ping downloads.rclone.org from unraid?

So did you try checking your firewall or DNS settings like it says? It can't download the binary from the rclone server.

Have you looked at the rclone documentation?

You can call rcloneorig instead of rclone and feed it the --config flag like so: rcloneorig --config Followed of course by the new path

@DazedAndConfused Here you go