EC2: unsupported protocol scheme ""

[byrnedo]

I keep getting this error for various commands when running on an aws instance. Is the base url screwed up or something??

This happens from the docker side doing docker volume create --driver rexray --opt size=1 --name test as well.

>$ rexray volume get
DEBU[0000] updated log level                             logLevel=debug
INFO[0000] [linux]                                      
INFO[0000] [docker]                                     
INFO[0000] [ec2]                                        
DEBU[0000] core get drivers                              osDrivers=[linux] storageDrivers=[ec2] volumeDrivers=[docker]
INFO[0000] os driver initialized                         provider=linux
INFO[0000] volume driver initialized                     provider=docker
INFO[0000] storage driver initialized                    provider=ec2
FATA[0000] Get /?AWSAccessKeyId=XXX&Action=DescribeVolumes&Signature=YYY&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=ZZZ&Version=2015-03-01: unsupported protocol scheme ""

My conf looks like this:

rexray:
  logLevel: debug
  storageDrivers:
    - ec2
aws:
  accessKey: XXX
  secretKey: YYY
  region: eu-central-1

[clintkitson]

Is it an intermittent error or when any commands are requested?

It looks like it is complaining about the API version we are using.

On Wednesday, February 3, 2016, Donal Byrne notifications@github.com
wrote:

I keep getting this error for various commands when running on an aws
instance. Is the base url screwed up or something??

This happens from the docker side doing docker volume create --driver
rexray --opt size=1 --name test as well.

$ rexray volume get
DEBU[0000] updated log level logLevel=debug
INFO[0000] [linux]
INFO[0000] [docker]
INFO[0000] [ec2]
DEBU[0000] core get drivers osDrivers=[linux] storageDrivers=[ec2] volumeDrivers=[docker]
INFO[0000] os driver initialized provider=linux
INFO[0000] volume driver initialized provider=docker
INFO[0000] storage driver initialized provider=ec2
FATA[0000] Get /?AWSAccessKeyId=XXX&Action=DescribeVolumes&Signature=YYY&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=ZZZ&Version=2015-03-01: unsupported protocol scheme ""

My conf looks like this:

rexray:
logLevel: debug
storageDrivers:
- ec2
aws:
accessKey: XXX
secretKey: YYY
region: eu-central-1

—
Reply to this email directly or view it on GitHub
#279.

[byrnedo]

Happens with any command.
The rexray version by the way:

Binary: /usr/bin/rexray
SemVer: 0.3.1
OsArch: Linux-x86_64
Branch: v0.3.1
Commit: bf4d6eec8c931b10d1ec187de052a23c09681ac6
Formed: Wed, 30 Dec 2015 21:12:44 UTC

[clintkitson]

Can you try it in another region?

On Wednesday, February 3, 2016, Donal Byrne notifications@github.com
wrote:

Happens with any command.
The rexray version by the way:

Binary: /usr/bin/rexray
SemVer: 0.3.1
OsArch: Linux-x86_64
Branch: v0.3.1
Commit: bf4d6ee
Formed: Wed, 30 Dec 2015 21:12:44 UTC

—
Reply to this email directly or view it on GitHub
#279 (comment).

[byrnedo]

yeah, I'll give it a go

[byrnedo]

Just FYI, removing the region flag makes no difference.
I haven't got round to launching in another region yet.

[clintkitson]

Ok. I am wondering the region you are in does not support some level of
API version by design or possibly unintentionally.

On Thursday, February 4, 2016, Donal Byrne notifications@github.com wrote:

Just FYI, removing the region flag makes no difference.
I haven't got round to launching in another region yet.

—
Reply to this email directly or view it on GitHub
#279 (comment).

[byrnedo]

It worked on us-east-1 no problem.

[clintkitson]

Any chance that there may be SSL problems in the original instance? Have
you tried from different AMIs in the same region?

On Thu, Feb 4, 2016 at 8:15 AM, Donal Byrne notifications@github.com
wrote:

It worked on us-east-1 no problem.

—
Reply to this email directly or view it on GitHub
#279 (comment).

[byrnedo]

Tried it on a fresh, stock ubuntu ami in eu-central-1 again and no good (
that was the 'same' ami, the amazon standard ubuntu, I tried in us-east-1).
Will try with some other ubuntu amis.

On 4 February 2016 at 17:48, Clinton Kitson notifications@github.com
wrote:

Any chance that there may be SSL problems in the original instance? Have
you tried from different AMIs in the same region?

On Thu, Feb 4, 2016 at 8:15 AM, Donal Byrne notifications@github.com
wrote:

It worked on us-east-1 no problem.

—
Reply to this email directly or view it on GitHub
#279 (comment).

—
Reply to this email directly or view it on GitHub
#279 (comment).

[byrnedo]

Ok, definitely something to do with either that one ami (stock ubuntu, ami-87564feb) or the region doesn't support it. I followed exact same procedure on this as in eu-west-1 and it just doesn't work.

FYI - some talk about the api in eu-central-1 being different: https://forums.aws.amazon.com/message.jspa?messageID=578908

Update: Tried different ubuntu lts ami and same thing.