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

scope tells me it's available at URLs that it's not available at #1678

Closed
jml opened this issue Jul 14, 2016 · 5 comments
Closed

scope tells me it's available at URLs that it's not available at #1678

jml opened this issue Jul 14, 2016 · 5 comments
Assignees
Labels
accuracy Incorrect information is being shown to the user; usually a bug bug Broken end user or developer functionality; not working as the developers intended it
Milestone

Comments

@jml
Copy link
Contributor

jml commented Jul 14, 2016

Running scope 0.16.1 on my Mac using docker-machine, I see the following:

$ ./scope launch
c46ebb9bc663573b9ca39000352cba4da5184c5ad61c9450f39ad37757298527
Weave Scope is reachable at the following URL(s):
  * http://10.32.0.1:4040/
  * http://192.168.99.100:4040/
  * http://10.0.2.15:4040/

However, when I click on these URLs, I get "address unreachable" errors for the first and third. Only the second URL is accessible.

Ideally, Scope would only tell me about URLs that I can actually reach. Failing that, the wording should be amended to be more truthful.

@jml jml added the bug Broken end user or developer functionality; not working as the developers intended it label Jul 14, 2016
@jml jml mentioned this issue Jul 14, 2016
@tomwilkie
Copy link
Contributor

Dupe of #1190

@tomwilkie tomwilkie reopened this Jul 14, 2016
@tomwilkie
Copy link
Contributor

Maybe not a dupe actually. But related.

@rade rade modified the milestones: August2016, September2016 Aug 17, 2016
@2opremio
Copy link
Contributor

2opremio commented Sep 8, 2016

Ideally, Scope would only tell me about URLs that I can actually reach. Failing that, the wording should be amended to be more truthful.

We should change the wording then, since the URLs that I can actually reach also depend on where you are connecting from (including firewalls and what not) and Scope cannot know about that.

@rade rade added the accuracy Incorrect information is being shown to the user; usually a bug label Jan 11, 2017
@rade rade modified the milestones: Backlog, Next Jul 14, 2017
@rade
Copy link
Member

rade commented Aug 3, 2017

We should change the wording then, since the URLs that I can actually reach also depend on where you are connecting from (including firewalls and what not) and Scope cannot know about that.

I don't think that this a big deal, but sure if we can make a small tweak to the wording (w/o turning it into a novel) then fine.

The main issue jml reported is that even for a purely local setup, scope may show a bunch of addresses that don't work. It would be nice if we were able to filter those out somehow.

@rade
Copy link
Member

rade commented Aug 3, 2017

IMO fixing this is only worthwhile if we can come up with a fairly clean and short solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accuracy Incorrect information is being shown to the user; usually a bug bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

No branches or pull requests

4 participants