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

Unable to browse on port 80 #1

Open
dalekurt opened this issue Dec 10, 2014 · 3 comments
Open

Unable to browse on port 80 #1

dalekurt opened this issue Dec 10, 2014 · 3 comments

Comments

@dalekurt
Copy link

Thank you for introducing me to Bamboo, I have Bamboo launched and I'm able to get to the Admin UI using the address http://IP:8000

I have deployed nginx using the marathon API

{
  "container": {
    "type": "DOCKER",
    "docker": {
      "image": "nginx",
      "network": "BRIDGE",
      "portMappings": [
        { "containerPort": 80, "hostPort": 0, "servicePort": 80, "protocol": "tcp" }
      ]
    }
  },
  "id": "nginx",
  "instances": "1",
  "cpus": "0.25",
  "mem": "256",
  "uris": []
}

And I then scaled it to 10 containers. When I login to the docker container for bamboo and have a look at /etc/haproxy.cfg file I can see the containers have been added to the file. However, I'm unable to browse port 80 on the Load Balancer (EC2 instance running bamboo docker container). I check the admin security group and confirmed that the port is open.

Any idea why this is?

@mbabineau
Copy link
Member

Great, sounds like you're close. Did you set up an ACL for nginx via the Bamboo admin interface?

Something like:

hdr(host) -i nginx.mycompany.com

You should then be able to hit nginx by passing the right Host header:

curl -H 'Host: nginx.mycompany.com' <bamboo_elb>

@dalekurt
Copy link
Author

Ahh! Let me try that. I'm currently working without a FQDN, I have to rely on the public FQDN of the EC2 instances.

By your example the nginx.mycompany.com has to be an A record which points to the IP of the bamboo_elb?

@mbabineau
Copy link
Member

CNAME and A records are both fine.

But for testing, you don't even need a DNS record. You just use manually set the Host header to fake it for HAProxy:

curl -H 'Host: fakedomain' <bamboo_elb>

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