Originally created by @skylarrudolph on GitHub (Feb 1, 2023).
Steps to reproduce
Add server (my-custom-domain).lan:13378
Failed to ping server
Expected behaviour
Should be prompted with Username/Password for Audiobookshelf application
Actual behaviour
Failed to ping server
Environment data
Audiobookshelf Version:0.9.61
Android App?
iOS App?
Android Issue
Android version:
Device model:
Stock or customized system:
iOS Issue
iOS Version: 16.2
iPhone model: 12
Originally created by @skylarrudolph on GitHub (Feb 1, 2023).
### Steps to reproduce
1. Add server (my-custom-domain).lan:13378
2. Failed to ping server
### Expected behaviour
- Should be prompted with Username/Password for Audiobookshelf application
### Actual behaviour
- Failed to ping server
### Environment data
Audiobookshelf Version:0.9.61
- [ ] Android App?
- [X] iOS App?
#### Android Issue
Android version:
Device model:
Stock or customized system:
#### iOS Issue
iOS Version: 16.2
iPhone model: 12
adam
added the bug label 2026-04-24 23:21:06 +02:00
So either your firewall is blocking it or you don't have the correct port forwarding if your phone can't ping your server.
@gh0sti commented on GitHub (Feb 1, 2023):
So either your firewall is blocking it or you don't have the correct port forwarding if your phone can't ping your server.
I have the same issue after upgrading to the latest version of the iOS app. It worked fine before the upgrade, after I can't connect to the server with a "Failed to ping server" error. The server is accessible in a browser on my phone using the same port.
@Hexaphim commented on GitHub (Feb 2, 2023):
I have the same issue after upgrading to the latest version of the iOS app. It worked fine before the upgrade, after I can't connect to the server with a "Failed to ping server" error. The server is accessible in a browser on my phone using the same port.
This issue also appeared on 2 iOS devices which previously worked.
Have downgraded both to last version to allow connectivity.
If you point it directly to an IP, it works, but we can't do this normally as we access through reverse proxy.
It is not a firewall issue as suggested by @gh0sti
@emmertex commented on GitHub (Feb 2, 2023):
This issue also appeared on 2 iOS devices which previously worked.
Have downgraded both to last version to allow connectivity.
If you point it directly to an IP, it works, but we can't do this normally as we access through reverse proxy.
It is not a firewall issue as suggested by @gh0sti
We're discussing this in Discord and trying to figure out how we should handle it.
At the moment the latest iOS app is restricted to using HTTPS for external connections.
This was the result of updating the deployment version to iOS 14.
@advplyr commented on GitHub (Feb 9, 2023):
We're discussing this in Discord and trying to figure out how we should handle it.
At the moment the latest iOS app is restricted to using HTTPS for external connections.
This was the result of updating the deployment version to iOS 14.
I’m having the same exact issue, fyi. iOS 16.3, app 0.9.60-beta. I can connect by manually putting in my IP rather than DDNS name ex. 90.677.68.1 vs audiobookshelf.ddnsname.com/13378
I keep getting ping error with DDNS name, all ports open on server side.
@dalto12593 commented on GitHub (Feb 12, 2023):
I’m having the same exact issue, fyi. iOS 16.3, app 0.9.60-beta. I can connect by manually putting in my IP rather than DDNS name ex. 90.677.68.1 vs audiobookshelf.ddnsname.com/13378
I keep getting ping error with DDNS name, all ports open on server side.
@CunningSquirrel commented on GitHub (Feb 15, 2023):
Bump, I’m having the exact same issue. ios16.3 cannot connect using custom domain after update. I’m in I.T so can assure you that my firewall and port forwarding rules are correct.
@CunningSquirrel commented on GitHub (Feb 15, 2023):
Bump, I’m having the exact same issue. ios16.3 cannot connect using custom domain after update. I’m in I.T so can assure you that my firewall and port forwarding rules are correct.
While waiting for the next release I’m just using the full IP address of my
hosted server.
On Wed, Feb 15, 2023 at 11:39 AM Kyle Gradwell @.***>
wrote:
Bump, I’m having the exact same issue. ios16.3 cannot connect using custom
domain after update. I’m in I.T so can assure you that my firewall and port
forwarding rules are correct.
@dalto12593 commented on GitHub (Feb 15, 2023):
While waiting for the next release I’m just using the full IP address of my
hosted server.
On Wed, Feb 15, 2023 at 11:39 AM Kyle Gradwell ***@***.***>
wrote:
> Bump, I’m having the exact same issue. ios16.3 cannot connect using custom
> domain after update. I’m in I.T so can assure you that my firewall and port
> forwarding rules are correct.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/advplyr/audiobookshelf-app/issues/538#issuecomment-1431836353>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A45QZS4HNFKOZWVS2NAYCDTWXUPGXANCNFSM6AAAAAAUNCVHE4>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @skylarrudolph on GitHub (Feb 1, 2023).
Steps to reproduce
Expected behaviour
Actual behaviour
Environment data
Audiobookshelf Version:0.9.61
Android Issue
Android version:
Device model:
Stock or customized system:
iOS Issue
iOS Version: 16.2
iPhone model: 12
@gh0sti commented on GitHub (Feb 1, 2023):
So either your firewall is blocking it or you don't have the correct port forwarding if your phone can't ping your server.
@Hexaphim commented on GitHub (Feb 2, 2023):
I have the same issue after upgrading to the latest version of the iOS app. It worked fine before the upgrade, after I can't connect to the server with a "Failed to ping server" error. The server is accessible in a browser on my phone using the same port.
@emmertex commented on GitHub (Feb 2, 2023):
This issue also appeared on 2 iOS devices which previously worked.
Have downgraded both to last version to allow connectivity.
If you point it directly to an IP, it works, but we can't do this normally as we access through reverse proxy.
It is not a firewall issue as suggested by @gh0sti
@gh0sti commented on GitHub (Feb 2, 2023):
Does it still happen on iOS 16.3?
@Hexaphim commented on GitHub (Feb 2, 2023):
I just upgraded to iOS 16.3 to test this out, and it does not work on iOS 16.3 either.
@emmertex commented on GitHub (Feb 8, 2023):
[log] - [Axios] Making request to http://audiobook.url.com/ping
⚡️ [error] - Axios error code {"message":"Network Error","name":"Error","stack":"@capacitor://localhost/_nuxt/22a3f3e.js:2:190849\n@capacitor://localhost/_nuxt/22a3f3e.js:2:189807","config":{"url":"http://audiobook.url.com/ping","method":"get","headers":{"Accept":"application/json, text/plain, /"},"baseURL":"http://localhost:3000/","transformRequest":[null],"transformResponse":[null],"timeout":3000,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false}}}
⚡️ [error] - Server check failed {"message":"Network Error","name":"Error","stack":"@capacitor://localhost/_nuxt/22a3f3e.js:2:190849\n@capacitor://localhost/_nuxt/22a3f3e.js:2:189807","config":{"url":"http://audiobook.url.com/ping","method":"get","headers":{"Accept":"application/json, text/plain, /"},"baseURL":"http://localhost:3000/","transformRequest":[null],"transformResponse":[null],"timeout":3000,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false}}}
@advplyr commented on GitHub (Feb 9, 2023):
We're discussing this in Discord and trying to figure out how we should handle it.
At the moment the latest iOS app is restricted to using HTTPS for external connections.
This was the result of updating the deployment version to iOS 14.
@dalto12593 commented on GitHub (Feb 12, 2023):
I’m having the same exact issue, fyi. iOS 16.3, app 0.9.60-beta. I can connect by manually putting in my IP rather than DDNS name ex. 90.677.68.1 vs audiobookshelf.ddnsname.com/13378
I keep getting ping error with DDNS name, all ports open on server side.
@advplyr commented on GitHub (Feb 12, 2023):
This will be fixed in the next release
@CunningSquirrel commented on GitHub (Feb 15, 2023):
Bump, I’m having the exact same issue. ios16.3 cannot connect using custom domain after update. I’m in I.T so can assure you that my firewall and port forwarding rules are correct.
@dalto12593 commented on GitHub (Feb 15, 2023):
While waiting for the next release I’m just using the full IP address of my
hosted server.
On Wed, Feb 15, 2023 at 11:39 AM Kyle Gradwell @.***>
wrote:
@advplyr commented on GitHub (Feb 20, 2023):
Fixed in v0.9.62-beta