I have read the Nov 24 thread about Internxt-cli & WebDav. My configuration is different, and I’m likely using a different internxt-cli version.
internxt-cli (version 1.5.0) is in a docker container and running webdav. The webdav does not take credentials & does not have a self-signed certificate, that I know of. Duplicati, in another container, can communicate and use the container. Well, it is writing chunks without error.
I have a duplicacy container created from ghcr.io/hotio/duplicacy. It’s the web GUI. The GUI does not allow entering nothing for username and password. (In Duplicati, I can get by entering “user” for a name.) Given this restriction, I jumped into the container and am trying to use the CLI to initialize a repo.
# duplicacy:/app/.duplicacy-web/bin# ./duplicacy_linux_x64_3.2.3 init -e mybackup webdav://user@internxt_duplicacy:3005//Backups/d
Enter the WebDAV password:
Failed to load the WebDAV storage at webdav://user@internxt_duplicacy:3005//Backups/d: Maximum backoff reached
Blank or anything for password has the same result.
What does that error mean? Is there a verbose mode to CLI or a place to check logs?
EDIT: I found the verbose option. I missed it the first time. Duplicacy was expecting an https response. I configured the command to request an http request by using webdav-http:// format. The init took. Some files are in the cloud. I am now at the MKCOL snapshots error the top Internxt post referred to.
URL request 'MKCOL snapshots' returned status code 400
Its error code is 400 rather than 409.