Originally created by @colvdv on GitHub (Oct 15, 2024).
What was the Problem?
When attempting to connect the audiobookshelf app to the server, the "Submit" button doesn't respond to touches; it acts like nothing happened.
White I've tried:
Restarting the App
Restarting the Phone
Reinstalling the App
It should be noted that I am able to access the server via the web browser, just not the audiobookshelf app. So the device is able to connect to the server.
Steps to Reproduce the Issue
Go to Add New Server
Enter Server Address
Press Submit... and nothing happens
What was Expected?
Press Submit button, app then proceeds to Username and Password entry screen.
Phone Model
Samsung Galaxy S23 FE
Phone OS
Android 13
Audiobookshelf App Version
Android App - 0.9.76
Installation Source
Google Play Store
Additional Notes
This server is connected through NordVPN's Meshnet service. We can verify that the connection is working through the web browser, but for some reason, not the app?
Originally created by @colvdv on GitHub (Oct 15, 2024).
### What was the Problem?
When attempting to connect the audiobookshelf app to the server, the "Submit" button doesn't respond to touches; it acts like nothing happened.
White I've tried:
- Restarting the App
- Restarting the Phone
- Reinstalling the App
It should be noted that I am able to access the server via the web browser, just not the audiobookshelf app. So the device is able to connect to the server.
### Steps to Reproduce the Issue
1. Go to Add New Server
2. Enter Server Address
3. Press Submit... and nothing happens
### What was Expected?
Press Submit button, app then proceeds to Username and Password entry screen.
### Phone Model
Samsung Galaxy S23 FE
### Phone OS
Android 13
### Audiobookshelf App Version
Android App - 0.9.76
### Installation Source
Google Play Store
### Additional Notes
This server is connected through NordVPN's Meshnet service. We can verify that the connection is working through the web browser, but for some reason, not the app?
adam
added the bugandroid labels 2026-04-24 23:47:22 +02:00
Not sure how the meshnet works, but if it's doing something similar to forward authentication, it will not work with the app. Forward authentication is not supported by the app and is not planned to be added.
@nichwall commented on GitHub (Oct 15, 2024):
Not sure how the meshnet works, but if it's doing something similar to forward authentication, it will not work with the app. Forward authentication is not supported by the app and is not planned to be added.
Edit: explanation here https://github.com/advplyr/audiobookshelf-app/issues/1155#issuecomment-2031674669
Not sure how the meshnet works, but if it's doing something similar to forward authentication, it will not work with the app. Forward authentication is not supported by the app and is not planned to be added.
It does indeed work over Meshnet. I have been using it this way for months and it works just fine for several devices. The issue is that the Audiobookshelf app isn't allowing me to press "Submit" after entering the server address.
@colvdv commented on GitHub (Oct 15, 2024):
> Not sure how the meshnet works, but if it's doing something similar to forward authentication, it will not work with the app. Forward authentication is not supported by the app and is not planned to be added.
It does indeed work over Meshnet. I have been using it this way for months and it works just fine for several devices. The issue is that the Audiobookshelf app isn't allowing me to press "Submit" after entering the server address.
Does the app work if you connect directly and not through the meshnet?
That isn't an option since this device isn't local and is only remote, hence the use of Meshnet in the first place. It was working fine a few months ago on the same device, but then the server was reinstalled and the address changed in the process. Going to reconnect it is where I ran into the issue.
@colvdv commented on GitHub (Oct 15, 2024):
> Does the app work if you connect directly and not through the meshnet?
That isn't an option since this device isn't local and is only remote, hence the use of Meshnet in the first place. It was working fine a few months ago on the same device, but then the server was reinstalled and the address changed in the process. Going to reconnect it is where I ran into the issue.
Was the server reinstalled recently or had the client attempted to connect, either signing out/in or switching between accounts? The most recent app update was 2 months ago, but there has not been much work in the apps in at least 6 months so not sure what would have changed. Do you know what app version was working with the meshnet?
@nichwall commented on GitHub (Oct 15, 2024):
Was the server reinstalled recently or had the client attempted to connect, either signing out/in or switching between accounts? The most recent app update was 2 months ago, but there has not been much work in the apps in at least 6 months so not sure what would have changed. Do you know what app version was working with the meshnet?
Was the server reinstalled recently or had the client attempted to connect, either signing out/in or switching between accounts? The most recent app update was 2 months ago, but there has not been much work in the apps in at least 6 months so not sure what would have changed. Do you know what app version was working with the meshnet?
I believe the latest version was working before the server reinstall. I just went in to add the new server via the app and the submit button wouldn't let me proceed.
The exact same configuration is working as expected on several other devices.
@colvdv commented on GitHub (Oct 15, 2024):
> Was the server reinstalled recently or had the client attempted to connect, either signing out/in or switching between accounts? The most recent app update was 2 months ago, but there has not been much work in the apps in at least 6 months so not sure what would have changed. Do you know what app version was working with the meshnet?
I believe the latest version was working before the server reinstall. I just went in to add the new server via the app and the submit button wouldn't let me proceed.
The exact same configuration is working as expected on several other devices.
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 @colvdv on GitHub (Oct 15, 2024).
What was the Problem?
When attempting to connect the audiobookshelf app to the server, the "Submit" button doesn't respond to touches; it acts like nothing happened.
White I've tried:
It should be noted that I am able to access the server via the web browser, just not the audiobookshelf app. So the device is able to connect to the server.
Steps to Reproduce the Issue
What was Expected?
Press Submit button, app then proceeds to Username and Password entry screen.
Phone Model
Samsung Galaxy S23 FE
Phone OS
Android 13
Audiobookshelf App Version
Android App - 0.9.76
Installation Source
Google Play Store
Additional Notes
This server is connected through NordVPN's Meshnet service. We can verify that the connection is working through the web browser, but for some reason, not the app?
@nichwall commented on GitHub (Oct 15, 2024):
Not sure how the meshnet works, but if it's doing something similar to forward authentication, it will not work with the app. Forward authentication is not supported by the app and is not planned to be added.
Edit: explanation here https://github.com/advplyr/audiobookshelf-app/issues/1155#issuecomment-2031674669
@colvdv commented on GitHub (Oct 15, 2024):
It does indeed work over Meshnet. I have been using it this way for months and it works just fine for several devices. The issue is that the Audiobookshelf app isn't allowing me to press "Submit" after entering the server address.
@nichwall commented on GitHub (Oct 15, 2024):
Does the app work if you connect directly and not through the meshnet?
@colvdv commented on GitHub (Oct 15, 2024):
That isn't an option since this device isn't local and is only remote, hence the use of Meshnet in the first place. It was working fine a few months ago on the same device, but then the server was reinstalled and the address changed in the process. Going to reconnect it is where I ran into the issue.
@nichwall commented on GitHub (Oct 15, 2024):
Was the server reinstalled recently or had the client attempted to connect, either signing out/in or switching between accounts? The most recent app update was 2 months ago, but there has not been much work in the apps in at least 6 months so not sure what would have changed. Do you know what app version was working with the meshnet?
@colvdv commented on GitHub (Oct 15, 2024):
I believe the latest version was working before the server reinstall. I just went in to add the new server via the app and the submit button wouldn't let me proceed.
The exact same configuration is working as expected on several other devices.