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

visor does not connect to / apppear in hypervisor on other side of router #398

Closed
0pcom opened this issue Jun 8, 2020 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@0pcom
Copy link
Collaborator

0pcom commented Jun 8, 2020

Describe the bug
the visor does not appear in the hypervisor when the hypervisor is on the other side of the (official skyminer) router

Environment information:

  • OS: Archlinux, ArchlinuxARM
  • Platform: x86_64, aarch64
    (desktop, official skyminer)

Steps to Reproduce
Using the official skyminer (with port forwarding previously configured on the router)-

  • install skywire on desktop (x86_64) and skyminer
    (freshly built to the latest commits to master today)
  • generate hypervisor and visr configs
  • copy hypervisor public key into visor config
  • start visor and hypervisor

Actual behavior
Visor does not appear in hypervisor interface. Visor's terminal output indicates "dialing" the hypervisor public key repeatedly.

Expected behavior
Visor appears in hypervisor interface.

Additional context
My guess is that the router is blocking the connection.

it was my understanding that this was supposed to work, from this article of documentation
https://github.com/SkycoinProject/skywire-mainnet/wiki/Run-HypervisorUI-on-local-machine

@0pcom 0pcom added the bug Something isn't working label Jun 8, 2020
@jdknives
Copy link
Member

@0pcom Are you sure that both the visor and the hypervisor use the same deployment? So are you sure the hypervisor was using the production deployment (and consequently that you did not use the -t flag) Can you check give us the logs for the hypervisor and visor in question? Sounds like a configuration or dmsg issue. As long as both visor and hypervisor have an internet connection, everything should work regardless of router configuration.

@0pcom
Copy link
Collaborator Author

0pcom commented Jun 26, 2020

I have not had time to conduct further tests. I am reasonably certain that the -t flag was not used but I will verify this the first chance I have.

@jdknives
Copy link
Member

Cannot reproduce this so will close for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants