concourse 4.2.1 - web login is redirecting to 127.0.0.1

[vaisyarajuraju123]

I am running concourse latest version (from Docker-compose.yml) in a ubuntu 18.0.4 Server and I could access the concourse web UI after bringing up the docker-compose however on login, it redirect the the request to 127.0.0.1 instead of the actual ubuntu server IP. Is there any way to fix it by keeping the server IP instead of redirecting to local server IP 127.0.0.1

[larssb]

Hi @vaisyarajuraju,

Are you sure that you have set the --external-url as described ind Docker run installation?
I think what you have done is likely that you wrote http://localhost:8080 or http://127.0.0.1:8080 in your docker-commpose.yml file or in the in --external-url environment variable to docker run. If you want the WEB-UI to go to your IP (192.168.1.18) ... that is what you should specify as the value to --external-url.

[kobylyanskiy]

I'm issuing this trouble too. Need to replace 127.0.0.1 with my server IP address to make everything work.

[jiaoyan2017]

Same issue.
fly -t blu-ci login
logging in to team 'main'

navigate to the following URL in your browser:

http://x.x.x.x:8080/sky/login?redirect_uri=http://127.0.0.1:38446/auth/callback

In browser, I'm also redirected to 127.0.0.1.

[larssb]

Try with a domainname, that works fine.

[dperezmavro]

Facing this problem here as well. In my case I am running concourse 4.2.2 on GKE and I need to provide the load-balancer IP for this parameter, which I don't know at the time of cluster creation (as the load balancer does not exist...).

Is there any default value that would tell concourse to use the server-ip instead?

Edit: The current workaround to this to create a reserved IP in GCP load-balancing, and specify that as part of the chart's values (using chart concourse-3.0.1):

web:
  service:
    type: LoadBalancer
    loadBalancerIP: x.x.x.x
concourse:
  web:
    externalUrl: "http://x.x.x.x"

[mattskone]

Amplifying above, the external URL also seems to require the port (8080), but I have observed that setting either the --external-url command arg or the CONCOURSE_EXTERNAL_URL environment variable both work.

[larssb]

Hi @mattskone ... exactly and thank you for trying it.

@dperezmavro, @vaisyarajuraju, @jiaoyan2017 and @kobylyanskiy please do that as well. Also, I'm sure that if you don't configure the ...EXTERNAL_URL... it will default to 127.0.0.1.

See:

The addition of the --external-url flag is not technically necessary, so if you're just testing things it's safe to omit it. Concourse uses it as a base when generating URLs to itself, so you won't want those to be the default http://127.0.0.1:8080 URL when you're developing on a different machine than the server.

From Concourse setup docs <-- it is actually clearly stated there.
So read-up on it >> try it out and come back and close the case when you have it working ;-).

[vito]

Closing as it sounds like a configuration issue. 👍

[ajaysheoran2323]

where do I need to update this --external-url . I setup concourse using helm chart and I dont have values.yaml file.

[sanjaykmruk]

@ajaysheoran2323 you can create a values.yml file and set the value there as

concourse:
web:
externalUrl: "external url"

and refer this value.yaml file on helm install command like this : helm install -f path-to-values.yaml-file stable/concourse