Originally created by @saurabh2804 on GitHub (Nov 5, 2021).
I have the latest Android app (installed just now from Android play store). On initial installation, once I add my URL (I have everything setup behind a reverse proxy), it keeps showing "Login success" and "Connecting to socket". This message never goes away. On force closing this, and opening the app again, the library is not populated. I also can't click on the "Main" button (with a small database sign). I should be able to click on it to have the option of changing over to another database.
On the web page, I can browse my library, but nothing plays. on portainer, I can see the following on the last lines of the log:
Originally created by @saurabh2804 on GitHub (Nov 5, 2021).
I have the latest Android app (installed just now from Android play store). On initial installation, once I add my URL (I have everything setup behind a reverse proxy), it keeps showing "Login success" and "Connecting to socket". This message never goes away. On force closing this, and opening the app again, the library is not populated. I also can't click on the "Main" button (with a small database sign). I should be able to click on it to have the option of changing over to another database.
On the web page, I can browse my library, but nothing plays. on portainer, I can see the following on the last lines of the log:
```
[2021-11-05T10:48:06.497Z] INFO: Recieved ping
[2021-11-05T10:48:08.156Z] INFO: Recieved ping
[2021-11-05T10:48:34.270Z] INFO: Recieved ping
[2021-11-05T10:54:00.802Z] INFO: Recieved ping
```
It sounds like an issue with the reverse proxy. Have you checked out the reverse proxy solutions in the readme?
Audiobookshelf uses a Socket.IO connection. The audio player relies on that websocket connection to play audiobooks, that is why I'm pretty sure it is your reverse proxy setup.
Received ping tells us your server is getting messages from the client but not the other way around.
@advplyr commented on GitHub (Nov 5, 2021):
It sounds like an issue with the reverse proxy. Have you checked out the reverse proxy solutions in the readme?
Audiobookshelf uses a Socket.IO connection. The audio player relies on that websocket connection to play audiobooks, that is why I'm pretty sure it is your reverse proxy setup.
Received ping tells us your server is getting messages from the client but not the other way around.
Thanks a lot for acting on my problem. However the problem seems to persist. Once I put in my login details, it says:
Login Success!
Connecting socket
It is stuck there. If I force close it, and start it again, the cloud symbol (top right) just shows 3 dot progress bar. It never actually does anything.
I am using the cloudflare with nginx reverse proxy manager. I tried unchecking the "common exploit" in the proxy manager, but it didn't help.
Connecting the phone to the Local network through wireguard, and entering the network address and port of the app connected without getting stuck on the "Connecting socket". I was able to switch to my actual library/database and the books populated.
Upon disconnecting from the Server Network and connecting through the URL, The problem appeared again.
@saurabh2804 commented on GitHub (Nov 8, 2021):
Thanks a lot for acting on my problem. However the problem seems to persist. Once I put in my login details, it says:
```
Login Success!
Connecting socket
```
It is stuck there. If I force close it, and start it again, the cloud symbol (top right) just shows 3 dot progress bar. It never actually does anything.
I am using the cloudflare with nginx reverse proxy manager. I tried unchecking the "common exploit" in the proxy manager, but it didn't help.
Connecting the phone to the Local network through wireguard, and entering the network address and port of the app connected without getting stuck on the "Connecting socket". I was able to switch to my actual library/database and the books populated.
Upon disconnecting from the Server Network and connecting through the URL, The problem appeared again.
I'm not familiar with the cloudflare with nginx reverse proxy manager. Are you able to compare the config generated from that with some of the other users working solutions with nginx?
There was some discussion today about nginx reverse proxy here: https://github.com/advplyr/audiobookshelf/discussions/126#discussioncomment-1526384
@advplyr commented on GitHub (Nov 9, 2021):
I'm not familiar with the cloudflare with nginx reverse proxy manager. Are you able to compare the config generated from that with some of the other users working solutions with nginx?
There was some discussion today about nginx reverse proxy here: https://github.com/advplyr/audiobookshelf/discussions/126#discussioncomment-1526384
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 @saurabh2804 on GitHub (Nov 5, 2021).
I have the latest Android app (installed just now from Android play store). On initial installation, once I add my URL (I have everything setup behind a reverse proxy), it keeps showing "Login success" and "Connecting to socket". This message never goes away. On force closing this, and opening the app again, the library is not populated. I also can't click on the "Main" button (with a small database sign). I should be able to click on it to have the option of changing over to another database.
On the web page, I can browse my library, but nothing plays. on portainer, I can see the following on the last lines of the log:
@advplyr commented on GitHub (Nov 5, 2021):
It sounds like an issue with the reverse proxy. Have you checked out the reverse proxy solutions in the readme?
Audiobookshelf uses a Socket.IO connection. The audio player relies on that websocket connection to play audiobooks, that is why I'm pretty sure it is your reverse proxy setup.
Received ping tells us your server is getting messages from the client but not the other way around.
@advplyr commented on GitHub (Nov 8, 2021):
This turned out to be a bug in the app fixed in the latest release. See #29
@saurabh2804 commented on GitHub (Nov 8, 2021):
Thanks a lot for acting on my problem. However the problem seems to persist. Once I put in my login details, it says:
It is stuck there. If I force close it, and start it again, the cloud symbol (top right) just shows 3 dot progress bar. It never actually does anything.
I am using the cloudflare with nginx reverse proxy manager. I tried unchecking the "common exploit" in the proxy manager, but it didn't help.
Connecting the phone to the Local network through wireguard, and entering the network address and port of the app connected without getting stuck on the "Connecting socket". I was able to switch to my actual library/database and the books populated.
Upon disconnecting from the Server Network and connecting through the URL, The problem appeared again.
@advplyr commented on GitHub (Nov 9, 2021):
I'm not familiar with the cloudflare with nginx reverse proxy manager. Are you able to compare the config generated from that with some of the other users working solutions with nginx?
There was some discussion today about nginx reverse proxy here: https://github.com/advplyr/audiobookshelf/discussions/126#discussioncomment-1526384