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
Relay server blocked in China #294
Comments
Wow. Hm, could they try replacing the server URL with one that only uses the (current) IP address?
That might not work because of the way that HTTP servers use the "Host:" header to figure out which site the client is trying to connect to, but since we don't tell the server its own hostname, I think it ought to work. A second fallback might be to modify the receiving machine's Please let me know if either of those works, or if we see evidence of the IP address being blocked too. |
Oh, if the transit relay is similarly DNS-blocked, they might also need to add The transit helper is probably at a stable address for the next 6 months. I might be moving the relay server in a month or two, at which point the IP address would change, but I might be able to leave a port-forwarding from the old one in place. So if it works for a while, but then stops working in a few months, check to see if the DNS entry has changed and update the |
I can't replicate this from Shanghai, but one of the obnoxious features of the great firewall is its inconsistency from location to location so this should not be taken as proof that there isn't blocking occurring somewhere in China. |
One of my receivers in China reported he can't connect to relay server. I think the default relay server has been polluted on DNS resolution in China. So it won't work for travelers to this tightly-censored state. Any ideas?
His log:
The text was updated successfully, but these errors were encountered: