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

Unable to resolve host "www.google.com": No address associated with hostname #2

Closed
lovebell opened this issue Apr 2, 2018 · 18 comments

Comments

@lovebell
Copy link

lovebell commented Apr 2, 2018

点击测试连接,等待很久,然后报错,
失败:Unable to resolve host "www.google.com": No address associated with hostname

s80402-103027 -

@kimw
Copy link

kimw commented Apr 2, 2018

  1. Do your key/passphare has =, ;, or \ included? If it is, gq-android is not work in this release. Please wait for next one.

  2. You can try turn off shadowsocks-android >> wait for 2-3 seconds >> trun on shadowsocks-android >> wait for 5-10 seconds >> then try to check connction. If this dose not work, wait for next release.

  3. You may know that the GoQuiet-android is not stable as of now. The so called RELEASE is for tech review preview (edit, sorry for the typo) only.

  4. (EDIT) If you truned TCP Fast Open on, turn it off and take a shoot. If this dose not work for you, please wait for the next so called release.

@lovebell
Copy link
Author

lovebell commented Apr 2, 2018

目前可以正常联网了!

做了几件事:①~④
①、重启手机,
②、检查“后台运行”是否生效,
1.Do your key/passphare has =, ;, or \ included? If it is, gq-android is not work in this release. Please wait for next one.
③、改成相对简单的密码,重新输入
2.You can try turn off shadowsocks-android >> wait for 2-3 seconds >> trun on shadowsocks-android >> wait for 5-10 seconds >> then try to check connction.
④、按照指示操作一遍,中间出现过“Handshake failure”提示,再打开就正常了

非常感谢~!

@koolwiki
Copy link

koolwiki commented Apr 2, 2018

@yhwfr1 我按照你这么操作也成功了,谢谢!

@chenshaoju
Copy link

This issue is pretty annoying. Sometimes need least 10 times to retry.

In my case, No necessity to restart shadowsocks or phone, Just disconnect in Shadowsocks, And wait 5 seconds and reconnect, After connected, Wait 5 seconds to test connectivity, If failed, just retry again.

But it's still can be working, Thank you for developing this plugin. 👍

@cbeuw
Copy link
Owner

cbeuw commented Sep 7, 2018

@chenshaoju
Sorry I've been quite lazy over the last few months. I didn't touch on this project at all and I almost forgot the existence of this bug. I just started working on it again. Don't have any clue yet but hopefully I'll be able to deliver a solution soon.

@cbeuw
Copy link
Owner

cbeuw commented Sep 9, 2018

This issue is weird. The app works perfectly fine on the emulator but not on metal. Maybe it's caused by the difference between x86 and arm? But the plugin works fine on arm-based Raspberry Pi.

I do see a pattern, however. Whenever the remote closes a connection first (which then triggers gq-client to close the ss connection on the same pipe), the thing won't work. However if it's ss that closes the connection first, the thing would run. I tried to make the client to never initiate the closing of an ss connection, the problem still persists.

@cbeuw
Copy link
Owner

cbeuw commented Sep 16, 2018

@madeye @Mygod
Did you encounter this problem (pressing connect doesn't always work) in kcptun or simple-obfs?

@madeye
Copy link

madeye commented Sep 17, 2018

@cbeuw Nope, I didn't see this issue.

BTW, we're now using go1.11 APIs to protect the socket, you may want to have a try. https://github.com/shadowsocks/overture/blob/4ea07479b42eef0e47d29cfa9559e37f995f0a58/core/utils/utils_android.go

@cbeuw
Copy link
Owner

cbeuw commented Sep 17, 2018

@madeye
Thanks for the reply! I will look into this new API.

@cbeuw
Copy link
Owner

cbeuw commented Sep 18, 2018

Yup it works when I use the vanilla net package from go1.11 instead of gotfo.

I decided to drop TCP Fast Open support. Before go1.11 gotfo was useful not only for TCP Fast Open, but also the fact that I don't have to compile the go compiler myself for the callback protector to work (not that it worked well). Now gotfo is just a burden. Its dirty hack is unmaintainable anyway and we'll wait for future go versions for the TCP Fast Open support.

@chenshaoju
Copy link

After a few times test, The v1.0.0 has fixed this issue.
Thank you!

@jutdoit
Copy link

jutdoit commented Oct 27, 2018

我的这个ssr用手机客户端连接能用,用电脑客户端却不能用,这是什么问题??

@chenshaoju
Copy link

你需要使用SSR的PC客户端才行,SS+GoQuite不能兼容SSR的混淆。

@narutojxl
Copy link

same problem, not solved by what @SCKC1 did, any idea?

@chenshaoju
Copy link

Please check your Shadowsocks client configure is correct.
Maybe case by wrong server IP, port, method, and password. Make sure is the same with the server.

@timothy2005
Copy link

Reason:
GCP(Google Cloud Platform) only open 2 ports by default: 80 and 443
If you use any other ports, you need allow it in Firewall setting, otherwise, you will get this error.

If you don`t know how to set firewall rule, the best way for you is: using 443 as the port number

@JackFe
Copy link

JackFe commented Mar 13, 2020

1、4.6.1升级至5.0.5
2、进入Shadowsocks应用详情:①设置为自启动;②省电策略设置为无限制
3、重启手机,恢复正常

@vyckey
Copy link

vyckey commented Mar 17, 2023

it doesn't work, anyone knows how to resolve it?

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