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

Fail to connect with 'wss://testnet-harbour.datahighway.com' #3

Closed
zhbh opened this issue May 27, 2020 · 7 comments
Closed

Fail to connect with 'wss://testnet-harbour.datahighway.com' #3

zhbh opened this issue May 27, 2020 · 7 comments

Comments

@zhbh
Copy link
Collaborator

zhbh commented May 27, 2020

this is my branch develop_sam, and run this project, it would show this issue:

I/chromium(15810): [INFO:CONSOLE(33)] "WebSocket connection to 'wss://testnet-harbour.datahighway.com/' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED", source: (33)

no more detail to view in the error log.

@zhbh
Copy link
Collaborator Author

zhbh commented May 27, 2020

it adds costom type to this way., and this our types.

@zhbh zhbh changed the title Fail to connect with 'wss://testnet-harbour.datahighway.com Fail to connect with 'wss://testnet-harbour.datahighway.com' May 27, 2020
@cgroeschel
Copy link

on the server side I see the request in reverse-proxy log like this:
reverse-proxy_nginx_1[16982]: 101.112.209.41 - - [27/May/2020:14:17:01 +0000] "GET / HTTP/1.1" 101 371051 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.116 Safari/537.36" "-"

@cgroeschel
Copy link

ERR_NAME_NOT_RESOLVED indicates issues resolving the hostname to the IP. Can you try:

  • to clear browser cache
  • ping the hostname and see if it resolves ok by your OS

@sheenhx
Copy link

sheenhx commented May 27, 2020

seems like 101.112.209.41 is Australia, Sydney

@sheenhx
Copy link

sheenhx commented May 27, 2020

Sam connected wss from chrome at home, so network is fine

@sheenhx
Copy link

sheenhx commented May 27, 2020

problem solved, it is android emulator DNS thing

@zhbh
Copy link
Collaborator Author

zhbh commented May 27, 2020

The issue was solved. That because is that my android simulator can be instability connected to the network on my laptop.

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

3 participants