Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

https CATTLE_URL not working? #1

Closed
marcovn opened this issue Sep 30, 2016 · 4 comments
Closed

https CATTLE_URL not working? #1

marcovn opened this issue Sep 30, 2016 · 4 comments

Comments

@marcovn
Copy link

marcovn commented Sep 30, 2016

Hi,

Great work you have done here. When trying to deploy the container on one of our environments we ran in to the issue that we have our rancher server setup on https only.

You get a stack trace like the one below. Opening the http port (as a workaround) fixes that but not very good for our security policy. Unfortunately my Ruby skills are not that great as I would tried to fix it.

Thanks,

E, [2016-09-30T11:31:10.430732 #5] ERROR -- : 784: unexpected token at '
30-9-2016 13:31:10
30-9-2016 13:31:10<title>400 Bad Request</title>
30-9-2016 13:31:10
30-9-2016 13:31:10

Bad Request


30-9-2016 13:31:10

Your browser sent a request that this server could not understand.

30-9-2016 13:31:10Reason: You're speaking plain HTTP to an SSL-enabled server port.

30-9-2016 13:31:10 Instead use the HTTPS scheme to access this URL, please.

30-9-2016 13:31:10


30-9-2016 13:31:10

30-9-2016 13:31:10Apache/2.4.7 (Ubuntu) Server at rancher.domain Port 443
30-9-2016 13:31:10
30-9-2016 13:31:10' (JSON::ParserError)
30-9-2016 13:31:10/usr/local/lib/ruby/2.3.0/json/common.rb:156:in parse' 30-9-2016 13:31:10/usr/local/lib/ruby/2.3.0/json/common.rb:156:inparse'
30-9-2016 13:31:10/usr/src/app/rancher_api.rb:17:in get' 30-9-2016 13:31:10/usr/src/app/rancher_api.rb:23:inblock (2 levels) in get_all'
30-9-2016 13:31:10/usr/src/app/rancher_api.rb:22:in loop' 30-9-2016 13:31:10/usr/src/app/rancher_api.rb:22:inblock in get_all'
30-9-2016 13:31:10/usr/src/app/reaper.rb:37:in each' 30-9-2016 13:31:10/usr/src/app/reaper.rb:37:ineach'
30-9-2016 13:31:10/usr/src/app/reaper.rb:37:in reap_hosts' 30-9-2016 13:31:10/usr/src/app/reaper.rb:21:inrun'
30-9-2016 13:31:10config.ru:24:in block (2 levels) in <main>

@ampedandwired
Copy link
Owner

Just pushed a fix (hopefully - I haven't got an https enabled Rancher handy). Could you try with the "latest" image in Docker Hub? If it's all good I'll cut another release.

@marcovn
Copy link
Author

marcovn commented Oct 4, 2016

Hi Charles,

Thanks for your fix. I can happily report it is working for us in our
environments. Very useful as we recycle our AWS based rancher hosts
frequently.

On Tue, Oct 4, 2016 at 6:00 AM, Charles Blaxland notifications@github.com
wrote:

Just pushed a fix (hopefully - I haven't got an https enabled Rancher
handy). Could you try with the "latest" image in Docker Hub? If it's all
good I'll cut another release.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQExDTW0bKgYWInO8aXR59H_MNUzl0w4ks5qwc9mgaJpZM4KK_ro
.

@ampedandwired
Copy link
Owner

Glad to hear it. I've tagged a new release, v0.1.1.

@marcovn
Copy link
Author

marcovn commented Oct 5, 2016

Awesome, I will deploy that tag and keep you posted.

On Wed, Oct 5, 2016 at 12:59 AM, Charles Blaxland notifications@github.com
wrote:

Glad to hear it. I've tagged a new release, v0.1.1.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQExDW-N3zdnFFz1RlrBRs-bRVZHJ_2Fks5qwtpngaJpZM4KK_ro
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants