Waseh

Yea but reaching 8.8.8.8 is fine. The plugin checks 8.8.8.8 first and only tries 1.1.1.1 if 8.8.8.8 fails.

That doesn't really make sense though since that should result in the "No internet - Skipping download and using existing archives" error. Are you sure you can reach the rclone webpage?

If the curl command doesnt solve it then the fix probably won't work either though since that's the fix im doing 😅 I just updated the plugin with a longer timeout.

Yea i haven't had time to push the fix (simple as it is). I'll see if I can get it done tonight.

Humor me a bit and try running it again with 5. If that still gives you an error I'll update the plugin with a more lax timeout

Well the plugin is doing exactly what it's supposed to. For some reason you can't connect to the rclone website to download the zip. Seems that you can't resolve the domain. Perhaps try increasing the timeout value and try the command again.

@Heciruam What happens if you run: curl --connect-timeout 5 --retry 3 --retry-delay 2 --retry-max-time 30 -o /boot/config/plugins/rclone/install/rclone-current.zip https://downloads.rclone.org/rclone-current-linux-amd64.zip

The plugin installs the newest version on install so just remove the plugin and install it again.

Having your plugins update automatically won't do much good if rclone is running when the update is triggered. The install didn't succeed. Try rebooting again if you cannot reinstall and/or you don't get any errors when you install

Sounds like you didn't have the new version installed. Are you getting any errors when you reinstall?

You could use the build in way to encrypt the config file but that just means that you have to either enter the password every time you run a command or include the password in the command kinda defeating the purpose. If you want to do it just run rclone config and follow the instructions for password protecting the config.

This seems to be the case for atleast some of you guys. Do you get any errors during the update?

Nope working fine here

Oh it won't affect performance at all - as soon as the command is entered the original binary handles everything so you won't gain anything by running it "directly" . If you check your running processes you'll already see rcloneorig and not rclone even though you invoked rclone.

@DZMM 'rcloneorig' is in fact the true rclone binary. When invoking 'rclone' (when using my plugin) you actually invoke a wrapper script that calls rcloneorig and injects the config path just as the example i posted above. This is done so the config can be kept on the flash drive as to keep it persistent across reboots, but to keep the command consistent with what it would be on other systems.

@DZMM Considering this only happens when you actually run a rclone command i don't think it's related to the plugin but perhaps more likely the rclone command itself. If somehow the wrapper is causing the problem you would be able to solve it by invoking: rcloneorig --config /boot/config/plugins/rclone-beta/.rclone.conf move /mnt/user/rclone_upload/google_vfs/ gdrive_media_vfs: -vv --drive-chunk-size 512M --checkers 3 --fast-list --transfers 2 --exclude .unionfs/** --exclude *fuse_hidden* --exclude *_HIDDEN --exclude .recycle** --exclude *.backup~* --exclude *.partial~* --bwlimit 9500k --tpslimit 4 This bypasses anything the wrapper is doing to the command. I would be surprised if this was the culprit though.

rclone could be doing any number of things so shutting it down gracefully really depends on what you've got going on. As mentioned earlier on this very page you can kill the proces if you want to to force the update - However standard warnings with killing processes apply.

No problem

I only asked you to do the ping because your post originally contained the no internet error that you removed in your edit 😛 Google how to kill a proces in Linux - look for rcloneorig when you call ps -A to find the pid Be aware that if you kill the proces you might screw something up if say you have a rclone remote mounted and don't close it gracefully

Try to ping 1.1.1.1 and 8.8.8.8 Edit: you just edited the post right? 😜 because now I don't see a no internet error which means that you don't really have an error except for the fact that perhaps rclone is running while trying to update? 😛

Yea i had pushed an incomplete change to the plugin by accident so it didn't ping 8.8.8.8 correctly. Glad it's working now

Well the logging clearly explains what's going on. The plugin determined that there isn't a connection to the internet. It does this by first pinging 8.8.8.8 and if that fails then pings 1.1.1.1 The question then remains why both of these checks are failing if, as it seems, the server actually is connected to the internet. Edit: seems like I pushed the wrong commit so it just pinged 1.1.1.1 twice. Try the new version (2018.09.10c) I just pushed

Try updating now Also be aware that the update wont complete if rclone is currently running.

And here i thought 1.1.1.1 would be reachable by anybody seeings as it's a DNS server run by cloudflare. So visiting 1.1.1.1 in your browser yields nothing?

What happens if you try to ping 1.1.1.1?