[Bug]: Android app only works with IPs, not hostnames #1226

Closed
opened 2026-04-24 23:54:20 +02:00 by adam · 3 comments
Owner

Originally created by @jaxley on GitHub (Jun 5, 2025).

I have verified that the bug is not already awaiting release

Yes

What was the Problem?

So far I've been unable to use any URL with a host name in it with the app. The only URLs that seem to work are bare IP addresses. I tried a local LAN hostname and an external DNS hostname but neither work. I tried adding the port number but that didn't change the outcome.

Image

Steps to Reproduce the Issue

  1. Open the app (after fresh install)
  2. Under "connect to server" type a url with a hostname like https://books florb.duckdns.org
  3. Click submit.
  4. View the error message (see attached screenshot)

What was Expected?

The app should resolve the DNS name and load the login page just like it does if you instead use the IP address of the server.

Phone Model

Galaxy s23 ultra

Phone OS

Android 15

Audiobookshelf App Version

Android App - 0.9.81

Installation Source

Google Play Store

Additional Notes

No response

Originally created by @jaxley on GitHub (Jun 5, 2025). ### I have verified that the [bug is not already awaiting release](https://github.com/advplyr/audiobookshelf-app/issues?q=is%3Aissue%20label%3A%22awaiting%20release%22) Yes ### What was the Problem? So far I've been unable to use any URL with a host name in it with the app. The only URLs that seem to work are bare IP addresses. I tried a local LAN hostname and an external DNS hostname but neither work. I tried adding the port number but that didn't change the outcome. ![Image](https://github.com/user-attachments/assets/6dd050a2-5637-49c5-8b4d-3904e430c534) ### Steps to Reproduce the Issue 1. Open the app (after fresh install) 2. Under "connect to server" type a url with a hostname like https://books florb.duckdns.org 3. Click submit. 4. View the error message (see attached screenshot) ### What was Expected? The app should resolve the DNS name and load the login page just like it does if you instead use the IP address of the server. ### Phone Model Galaxy s23 ultra ### Phone OS Android 15 ### Audiobookshelf App Version Android App - 0.9.81 ### Installation Source Google Play Store ### Additional Notes _No response_
adam added the bug label 2026-04-24 23:54:20 +02:00
adam closed this issue 2026-04-24 23:54:20 +02:00
Author
Owner

@Vito0912 commented on GitHub (Jun 5, 2025):

Did you make sure that the DNS entry resolved correctly? E.g. with nslookup

If so, did you make sure that it works in the browser? It looks like a configuration problem with your DNS-Server like the error tells you.

@Vito0912 commented on GitHub (Jun 5, 2025): Did you make sure that the DNS entry resolved correctly? E.g. with nslookup If so, did you make sure that it works in the browser? It looks like a configuration problem with your DNS-Server like the error tells you.
Author
Owner

@jaxley commented on GitHub (Jun 5, 2025):

I can reach the server in the browser using that url just fine. It's only via the app that it fails.

I just tried using Internet resolvers and that seems to work differently. Digging into my DNS setup now. Seeing some odd behavior.

@jaxley commented on GitHub (Jun 5, 2025): I can reach the server in the browser using that url just fine. It's only via the app that it fails. I just tried using Internet resolvers and that seems to work differently. Digging into my DNS setup now. Seeing some odd behavior.
Author
Owner

@jaxley commented on GitHub (Jun 6, 2025):

Okay, I did a bunch of TCP dump and Wireshark and looked at pihole logs. There is some issue with the wifi APs forwarding queries and appending the search domain to fqdn queries when they shouldn't be. Negative responses are getting returned sporadically from the AP. I

I did confirm that while the hostnames aren't working in the app, the DNS resolution in a browser is also broken. Closing.

@jaxley commented on GitHub (Jun 6, 2025): Okay, I did a bunch of TCP dump and Wireshark and looked at pihole logs. There is some issue with the wifi APs forwarding queries and appending the search domain to fqdn queries when they shouldn't be. Negative responses are getting returned sporadically from the AP. I I did confirm that while the hostnames aren't working in the app, the DNS resolution in a browser is also broken. Closing.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf-app#1226