Waseh

Community Developer
  • Posts

    203
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Waseh

  1. 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.

    • Like 1
  2. 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 

  3. 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.

  4. 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.

  5. 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 

  6. 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? 😛

  7. 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 :)

     

  8. Don't worry about it - glad we got it working ;)

     

    Yea that happened when you deleted the whole folder of rclone / rclone-beta as it contains the config. The commands I posted earlier would have prevented that from happening.