I figured "if that's where the installer puts profiles, I should use that folder too". That's why I moved the Wasabi profiles from the %ProgramFiles(86)% folder to the %ProgramFiles% folder, even though I read in the docs that the %APPDATA% location should be used. Cyberduck is a free open-source cloud stor. It also did not even create the %AppData%\Roaming\Cyberduck\Profiles folder. Cyberduck latest version: Share files with ease using this free program. Also note that the 64-bit MSI installer removed all files under the %ProgramFiles(86)%\Cyberduck CLI folder, except for the two Wasabi profiles in the Profiles subfolder, which I had manually copied there when I first installed the 32-bit CLI some 10 months ago. UPDATE: I was wrong - the problem was not due to using incorrect CLI syntax. It appears that on unchecking it Im not able to view/open websites too. It apparently installed 17 profiles to the %ProgramFiles%\Cyberduck CLI\Profiles folder (but not the Wasabi profiles, which is what caused my issue). If you uncheck that, does it prevent Cyberduck from connecting Yes, it does prevent the connection. That also works, so the CLI apparently will look in both of these folders for profiles. I also experimented a bit by creating the Profiles folder in *%AppData%\Roaming\Cyberduck*, and moving the 2 Wasabi profiles (east-1 and west-1) from %ProgramFiles%\Cyberduck CLI\Profiles folder to the %AppData%\Roaming\Cyberduck\Profiles folder. Of course, anytime you update your operating system you should be aware that your existing software applications may not always run correctly on the new installation. The connection will fail if the Comet Backup client is not running on the same machine. I manually copied the profiles to %ProgramFiles%\Cyberduck CLI\Profiles, and the CLI does see and use them. Comet Server on Windows consists of two parts: cometd.exe and.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |