-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
UI not starting with ui_dir in config file #166
Comments
@bscott can you show us what the config looks like? Specifying |
{ |
@bscott When you hit the index page (http://localhost:8500/) what do you get? Does it say "Consul Agent" or do a redirect? Also unrelated, but you will run into issues if you datacenter has periods in it. It makes the DNS parsing ambiguous. Instead, you might try making the datacenter "us-west-1", and if you want, set the |
@armon The node isn't even listening on port 8500 |
The default listen port for HTTP is 8500 unless configured otherwise. Is the agent even starting? |
@armon Yes, the agent is starting and joining the cluster. |
So when it starts, it should log the HTTP port. Can you try to curl port it is logging? Based on the response we can determine if it is loading the UI. |
I'm able to get the UI working on Linux, but not on Windows (version 0.2.1). Here's the output from curl: Windows:
^^^ No redirect Linux:
^^^ Provides a redirect to /ui/ Incidentally I've tried several forms of path in the consul json configuration file on Windows and none appear to work:
I hope that helps you track down the problem. |
Hey guys, I'll respond shortly , traveling at the moment. On Tuesday, May 27, 2014, Patrick Wyatt notifications@github.com wrote:
Brian Scott - DevOps and Automation Guy, Ruby/Rails Guy, all around Good |
@webcoyote Can you verify if this is happening with the latest build? Might be the same issue of running the older Consul build. |
@armon: The UI >does< work on Windows when I compiled the latest version from source (re: |
I'm still having this issue on latest build with Linux, but I'll test again. |
Closing. Please re-open if still an issue. |
I am encountering this issue. I Can enable the UI on the servers. However on a consul client, requests to
The
Removed |
Hi @cleung2010 - there's no difference in the client vs. server code path that I can see for the server. If you do a |
|
Actually - I get a 301 when running that |
I get a 200, but the response contains this:
When I |
Hmm - that's actually part of the static index.html page - so it looks like that might be getting served up properly by Consul's web server: https://github.com/hashicorp/consul/blob/master/ui/index.html#L44-L45
I don't follow what you mean by "Consul Agent on the response" there. Is that not serving up the same index.html? |
i am also getting same issue HTTP error code from Consul: 0 error
but when running same command "curl http://localhost:8500/ui/" inside the container , i am getting valid output. docker ps output in host =>
Inside the container =>
ls -ltr /ui |
@slackpad I mean this:
I also get a 200 and the same response on the body of the client if I do not specify |
Noticed that
The security group on AWS allows TCP inbound connection from 0.0.0.0/0 to 8500. Networking seems fine too.
|
@slackpad @hridyeshpant Got it working by adding this to my
As explained in #599 the client binds the HTTP address to localhost by default so within the client you're able to curl the I'd suggest to update the docs on the Web-UI page so that it explicitly states that the default config only enables the UI within |
@cleung2010
Log data will now stream in as it occurs:
my config file
and i am using setup from >>https://github.com/gliderlabs/docker-consul/tree/master/0.6/consul-server in local box outside the container
but inside the container, i am able to get page using curl -v -L localhost:8500 |
@hridyeshpant Can you check the port mapping for that container with |
@cleung2010 |
I am facing the issues in access the consul UI. Here is how I am starting it
Please suggest. Let me know if any details required. Thanks. |
@gvenka008c that's the correct behavior - Consul is trying to redirect you to /ui/ which is the location of the web UI. If you add a |
@slackpad Thanks. When I try to hit the URL http://xx.xxx.xxx.xx:8500/ui/ from the browser, it says "Failed to Open Page". I have opened the ports on the server but still the same problem.
|
@slackpad I started consul with -client argument and that fixed the issues.
|
Move contributing docs to Contributing.md
I cannot get the UI to start using the ui_dir directive in the config file, only via as a command line flag.
The text was updated successfully, but these errors were encountered: