Continue Listening Not Working on WAN

[tmurphy2792 27]

So I've had this issue for awhile now and I can't quite pinpoint when it started because it admittedly took me awhile to notice the pattern.

 

If I'm at home on WiFi, I can listen to audiobooks and podcasts no problem, and when I stop listening it marks my place for me to come back and resume (which is a pain on podcasts since they don't show on homepage continue listening section, but that's another post).

BUT if I go to listen to a book or podcast while away from home, everything will seem to work fine with a single key exception. The continue listening resume point will not update.

I'm open to the idea it's an issue with my nginx configuration since it only happens on WAN, but at the same time I've tested on windows desktop app and browser and this doesn't seem to be an issue with those.

 

Here is what I believe is pertinent info, including snippet of android logs where the error takes place.

Emby server:

4.9.3.0

Android app:

3.5.28

 

Logs snippet

Quote

ApiClient: Error in reportPlaybackProgress : Unexpected code Response{protocol=h2, code=404, message=, url=https://my server.com/emby/Sessions/Playing/Progress}

The file '/emby/Sessions/Playing/Progress' could not be found.

java.io.IOException

com.mb.android.apiinteraction.RequestHelper.lambda$executeSerialRequest$0(RequestHelper.java:189)

com.mb.android.apiinteraction.RequestHelper$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1154)

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:652)

java.lang.Thread.run(Thread.java:1563)

Wed Feb 11 22:28:49.572 GMT-06:00 2026 Error sending request to http://my server.com/emby/Sessions/Playing/Stopped: Unexpected code Response{protocol=h2, code=404, message=, url=https://my server.com/emby/Sessions/Playing/Stopped}

The file '/emby/Sessions/Playing/Stopped' could not

be found.

 

Any idea what could be causing this issue? Looks like I'm getting a 404 not found on the API call.

Is this a bug in the android app, or should I be investigating an issue with my nginx setup?

[tmurphy2792 27]

So just an update on this, I believe I have self resolved the issue here.

 

When setting up my external domain in the network settings on the server I left off the "https://" prefix. After changing this setting  my continue listening appears to work fine.

 

As embarrassing and waste of time as this post feels like, I guess I'll leave it up so someone else can learn from my dumb move, but I'd call this one solved.

[Luke 42077]

HI, thanks for following up !