-
Notifications
You must be signed in to change notification settings - Fork 35
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
Suddenly stopped working #25
Comments
Interesting. Does it work if you access an IP address directly, such as https://1.1.1.1 or https://8.8.8.8? It might be the case that the DNS servers aren't reachable for some reason... |
I get this error in Firefox when trying to access those ip addresses directly: Error response Error code: 502 Message: Unable to connect to host ('8.8.8.8', 80): [Errno 49] error while attempting to bind on address ('10.156.33.219', 0): can't assign requested address. Error code explanation: HTTPStatus.BAD_GATEWAY - Invalid responses from another server/proxy. |
Yesterday it randomly worked with the hotspot again but now when I tried it's back to not working. EDIT: |
Hi @thejoltjoker , How do we enable the ad-hoc network in MAC, I use MAC OC 14.2.1 (23C71) and I can't find the information at all. And can you share the steps to set IP and use DNS. Thanks in advance, |
@thejoltjoker hmm, I wonder if maybe your cellular connection's IP address changed? Is 10.156.33.219 your hotspot address (which probably wouldn't work) or your cellular connection's IP address? You can run the |
I've been using this for the past month with no problems, but suddenly yesterday it just started spitting out errors.
I've been using personal hotspot on my iPhone 13 Pro and connecting to it using a MacBook Pro M1 2021.
I tried using it with an ad-hoc network on the MacBook and it worked for a little while before giving me the same results.
I'd love to help develop a solution but I'm not quite sure where to start.
Error:
Assuming proxy will be accessed over hotspot (bridge100) at 172.20.10.1
Will connect to IPv4 servers over interface pdp_ip0 at 10.157.45.147
PAC URL: http://172.20.10.1:8088/wpad.dat
SOCKS Address: 172.20.10.1:9876
HTTP Proxy Address: 172.20.10.1:9877
Connections: 0
Total In: 0.00 MB
Total Out: 0.00 MB
Total: 0.00 MB
Errors: 19
Last 5 log messages:
172.20.10.5:64556: code 502, message Unable to connect to host ('detectportal.firefox.com', 80): Host ('detectportal.firefox.com', 80) could not be resolved
172.20.10.5:64557: code 502, message Unable to connect to host ('ssl.gstatic.com', 443): Host ('ssl.gstatic.com', 443) could not be resolved
172.20.10.5:64558: code 502, message Unable to connect to host ('detectportal.firefox.com', 80): Host ('detectportal.firefox.com', 80) could not be resolved
172.20.10.5:64559: code 502, message Unable to connect to host ('calendar.google.com', 443): Host ('calendar.google.com', 443) could not be resolved
172.20.10.5:64560: code 502, message Unable to connect to host ('ssl.gstatic.com', 443): Host ('ssl.gstatic.com', 443) could not be resolved
Shutting down.
The text was updated successfully, but these errors were encountered: