Audio books not showing played/not saving location

[jgauthier 13]

I've been listening to an audio book with multiple files.  After each file is listened to, it's never marked as played.

Additionally, my position is never saved. If I pop onto the web browser, and I hit play/stop the position is stored.

It just never stores/updates it from the Android app.

[Luke 37095]

 

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

 

[jgauthier 13]

I will do my best.  I do not see any way to present Android App logs. 

Server logs attached.  In the app screenshot you can see a saved session that I did from a web browser (clicked play and then stop)

My current chapter is 21.  NONE of the files ever get flagged as "played" automatically when listening to the audio book in the app

embyserver.7z

[jgauthier 13]

@Luke Is there additional information I can provide?

[jgauthier 13]

@LukeI'm wondering what a forward path on this issue might look like.  Currently I have to try and remember what file I am on as well as how far into it.  Having to search for my book location every time I go somewhere is tiring me out.

Edited December 15, 2023 by jgauthier

[Luke 37095]

@jgauthierare you using a VPN? If so, can you try turning that off and seeing how things compare? There's a lot of this in your server log:

2023-12-05 00:11:33.093 Debug Server: http/1.1 Response 404 to host3. Time: 0ms. http://emby_remote_ip/Sessions/Playing/Progress

It could be that something such as a vpn or reverse proxy is interfering with that request. If we get to the bottom of that, I think we solve your issue.

Thanks.

[jgauthier 13]

No VPN but indo use a reverse proxy for SSL termination.  I followed the guide on this forum to configure it.  I can post the config later (when I'm con front of a computer)

 

[jgauthier 13]

server {
    if ($host = emby.mydomain.org) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    listen 80;
    server_name emby.mydomain.org;

    return 301 https://$host$request_uri;

}

    ## Start of actual server blocks
server {

    listen 443 ssl;       ## Listens on port 443 IPv4 with http2 and ssl enabled
    proxy_buffering off;        ## Sends data as fast as it can not buffering large chunks.

    server_name emby.mydomain.org;    ## enter your service name and domain name here example emby.domainname.com
    ssl_certificate /etc/letsencrypt/live/emby.mydomain.org-0001/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/emby.mydomain.org-0001/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

     location / {
        proxy_pass  http://emby:8096;
        client_max_body_size 0;  
        proxy_hide_header X-Powered-By;  ## Hides nginx server version from bad guys.
        proxy_set_header Range $http_range;  ## Allows specific chunks of a file to be requested.
        proxy_set_header If-Range $http_if_range;  ## Allows specific chunks of a file to be requested.
        proxy_set_header X-Real-IP $remote_addr;  ## Passes the real client IP to the backend server.

        proxy_set_header Host $host;  ## Passes the requested domain name to the backend server.
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;  ## Adds forwarded IP to the list of IPs that were forwarded to the backend server.

        add_header 'Referrer-Policy' 'origin-when-cross-origin';
        add_header Strict-Transport-Security "max-age=15552000; preload" always;
        add_header X-Frame-Options "SAMEORIGIN" always;
        add_header X-Content-Type-Options "nosniff" always;
        add_header X-XSS-Protection "1; mode=block" always;

     ## WEBSOCKET SETTINGS ## Used to pass two way real time info to and from emby and the client.
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $http_connection;
    }

}

 

[Luke 37095]

I would compare your NGinx setup to this: 

You have GET requests coming into the server that should be POST. Something's not right.

[jgauthier 13]

I based my nginx setup from that post.  I looked through the nginx logs and those are both GET and POST requests happening back to back.

Those are an amazon firestick.  My android audio book doesn't seem to be doing that.

 

Firestick:

192.168.90.230 - - [18/Dec/2023:17:41:34 +0000] "POST /Sessions/Playing/Progress HTTP/1.1" 301 169 "-" "okhttp/4.9.2" "-"
192.168.90.230 - - [18/Dec/2023:17:41:34 +0000] "GET /Sessions/Playing/Progress HTTP/2.0" 404 34 "-" "okhttp/4.9.2" "-"

 

Audiobook (android)

274.338.265.97 - - [18/Dec/2023:17:43:53 +0000] "POST /Sessions/Playing/Progress HTTP/2.0" 204 0 "-" "okhttp/4.9.2" "-"
274.338.265.97 - - [18/Dec/2023:17:43:53 +0000] "POST /Sessions/Playing/Progress HTTP/2.0" 204 0 "-" "okhttp/4.9.2" "-"

 

[Luke 37095]

On the firestick,  Can you try sideloading our standard android app on the same device and see how that compares?

https://emby.media/emby-for-android.html

Thanks.

 

[jgauthier 13]

Sure, but I am not interested in listening to audio books on the firestick.  I listen to them on my phone (android) and that is where I am having issues with the progress markers, as well as "played" markers