Skip to main content
Android Enthusiasts

Return to Question

confirmed that this is a problem on multiple Android versions
Source Link
Ryan
Ryan
  • 405
  • 1
  • 9
  • 20

I have a PC whose name is "mypc". It's accessible on the local network.

https://mypc.local correctly displays its website when browsed from Mac, iOS, and itself.

However, using my Pixel 3 with Android 11, browsing to https://mypc.local says “This site can’t be reached”. ERR_NAME_NOT_RESOLVED.

Interestingly, if I remove the ".local" and try browsing just to https://mypc it, the browser finds the host correctly. It says "Your connection is not private" and ERR_CERT_AUTHORITY_INVALID (which just means my self-signed certificate isn't configured to expect "mypc" because it expects "mypc.local").

I've tried Brave Private, DuckDuckGo, and Chrome.

How can I fix my Android devicedevices to correctly use the .local hostname?

P.S. I've seen the following questions, but those answers don't apply to my case since my network router is correctly mapping mypc.local to the specific IP of that PC. Additionally, even Android is aware of how to resolve "mypc" to the correct IP, so I'm curious how to get it to treat "mypc.local" the same way.

P.P.S. I also just tried from an old Nexus 7 with Android 5.1.1. The results are basically the same as with Android 11. https://mypc.local/ does not work and says DNS_PROBE_FINISHED_NXDOMAIN. https://mypc finds the host correctly but says NET:ERR_CERT_AUTHORITY_INVALID.

I have a PC whose name is "mypc". It's accessible on the local network.

https://mypc.local correctly displays its website when browsed from Mac, iOS, and itself.

However, using my Pixel 3, browsing to https://mypc.local says “This site can’t be reached”. ERR_NAME_NOT_RESOLVED.

Interestingly, if I remove the ".local" and try browsing just to https://mypc it says "Your connection is not private" and ERR_CERT_AUTHORITY_INVALID (which just means my self-signed certificate isn't configured to expect "mypc" because it expects "mypc.local").

I've tried Brave Private, DuckDuckGo, and Chrome.

How can I fix my Android device to correctly use the .local hostname?

P.S. I've seen the following questions, but those answers don't apply to my case since my network router is correctly mapping mypc.local to the specific IP of that PC. Additionally, even Android is aware of how to resolve "mypc" to the correct IP, so I'm curious how to get it to treat "mypc.local" the same way.

I have a PC whose name is "mypc". It's accessible on the local network.

https://mypc.local correctly displays its website when browsed from Mac, iOS, and itself.

However, using my Pixel 3 with Android 11, browsing to https://mypc.local says “This site can’t be reached”. ERR_NAME_NOT_RESOLVED.

Interestingly, if I remove the ".local" and try browsing just to https://mypc, the browser finds the host correctly. It says "Your connection is not private" and ERR_CERT_AUTHORITY_INVALID (which just means my self-signed certificate isn't configured to expect "mypc" because it expects "mypc.local").

I've tried Brave Private, DuckDuckGo, and Chrome.

How can I fix my Android devices to correctly use the .local hostname?

P.S. I've seen the following questions, but those answers don't apply to my case since my network router is correctly mapping mypc.local to the specific IP of that PC. Additionally, even Android is aware of how to resolve "mypc" to the correct IP, so I'm curious how to get it to treat "mypc.local" the same way.

P.P.S. I also just tried from an old Nexus 7 with Android 5.1.1. The results are basically the same as with Android 11. https://mypc.local/ does not work and says DNS_PROBE_FINISHED_NXDOMAIN. https://mypc finds the host correctly but says NET:ERR_CERT_AUTHORITY_INVALID.

Tweeted twitter.com/StackAndroid/status/1322236856227008516
Source Link
Ryan
Ryan
  • 405
  • 1
  • 9
  • 20

Why can't I browse to my desktop using its .local hostname?

I have a PC whose name is "mypc". It's accessible on the local network.

https://mypc.local correctly displays its website when browsed from Mac, iOS, and itself.

However, using my Pixel 3, browsing to https://mypc.local says “This site can’t be reached”. ERR_NAME_NOT_RESOLVED.

Interestingly, if I remove the ".local" and try browsing just to https://mypc it says "Your connection is not private" and ERR_CERT_AUTHORITY_INVALID (which just means my self-signed certificate isn't configured to expect "mypc" because it expects "mypc.local").

I've tried Brave Private, DuckDuckGo, and Chrome.

How can I fix my Android device to correctly use the .local hostname?

P.S. I've seen the following questions, but those answers don't apply to my case since my network router is correctly mapping mypc.local to the specific IP of that PC. Additionally, even Android is aware of how to resolve "mypc" to the correct IP, so I'm curious how to get it to treat "mypc.local" the same way.