Duplicity

Install: UnsupportedBackendScheme: scheme not supported in url: s3+http://foo.woof.com/?

Asked by LarryK

Hi,

I installed Duplicity with the helpful damontimm [script][1] and [advice][2]. Used current release.

I also created an s3 bucket foo.woof.com. (Not the real name)

But when I run Duplicity (via the script), I get:

`UnsupportedBackendScheme: scheme not supported in url: s3+http://foo.woof.com/`

What should I do? Do I need to make S3 bucket foo.woof.com available via DNS? (I do know how to do that.)
Or something else?

I am using the `--s3-use-new-style` option.

Thanks,

Larry

  [1]: http://blog.damontimm.com/bash-script-incremental-encrypted-backups-duplicity-amazon-s3/
  [2]: http://blog.damontimm.com/how-to-automated-secure-encrypted-incremental-backups-amazon-s3-duplicity-os-x-or-ubuntu/

Question information

Language:
English Edit question
Status:
Solved
For:
Duplicity Edit question
Assignee:
No assignee Edit question
Solved by:
LarryK
Solved:
Last query:
Last reply:
Revision history for this message
LarryK (wexner) said : 		#1

I also tried with a simple bucket name that does not include dots. Same problem.

Also, another user is having same problem. He downgraded to Duplicity 0.6.06 and then it started working.
See http://serverfault.com/questions/187970/duplicity-no-longer-works-with-amazon-s3

Revision history for this message
edso (ed.so) said : 		#2

DId you try using duplicity directly on the command prompt? Does that work?

Also. Do you have boto installed?

Eventually. Run duplicity with the verbose switch -v9 from command line and from inside your script and post the results here.

regards ede/duply.net

Revision history for this message
edso (ed.so) said : 		#3

It says pretty clearly

UnsupportedBackendScheme

which means that duplicity does not know what to do with 's3+http' in your case, but it should. Scheme is another name for protocol here.

..ede/duply.net

Revision history for this message
Maarten Kossen (mpkossen) said : 		#4

+1 for a workaround until it has been fixed.

Revision history for this message
Maarten Kossen (mpkossen) said : 		#5

Well, I was too impatient. For those on an RPM-based system, check this link:

https://launchpad.net/duplicity/+milestone/0.6.06

I downloaded the package and downgraded it on my CentOS install. Everything works fine again. The command to downgrade on CentOS (i386) is:

yum downgrade --nogpgcheck duplicity duplicity-0.6.06-0.fdr.6.i386.rpm

Revision history for this message
LarryK (wexner) said : 		#6

My thanks to Kenneth for fixing the problem and issuing a patch. See the linked bug report for details.