Sonos and FLAC

Plex Players
,
1

Server Version#: 1.41.0.8994
Player Version#: Any and all but a specific example is Plexamp v4.11.2

I’m pulling my hair out and am here as a last resort. Unfortunately I’ve seen many similar posts on Sonos, Reddit, and here with no resolution. Ultimately the issue is that Sonos + Plex just cannot handle FLAC files. I can play FLAC files with Plexamp directly in web app, iOS, Windows desktop app, etc. no issue. I can play the same FLAC files on Sonos with SMB share with no issues. If I try to play those FLAC files either with the Sonos Plex service or “casting” from Plexamp or any Plex player, it’s just a constant struggle. Files either just won’t play at all, or they’ll skip, or if they do play they take forever to start and they’ll eventually stop playing or skip. Attempting to scrub will trigger one of the above issues. If I pause, and then press play, the file will either restart or just skip to next track (or skip multiple tracks). I have gig internet and most of my speakers are hardwired. Does anyone have any kind of solution? Is this a known bug being worked on? Is there any reasonable solution out there at all to get FLAC onto a decent multi-room system? I’ll be happy to provide logs. Are there any particular portions I should exclude? I see my IP and an auth token so seems like a bad idea to post in full.

2

FWIW. It seems like some sort of transcode issue, however, these files should not be transcoding. The console in Plex is spitting out thousands of lines that look like the below when I’m having issues.

[Req#148608/Transcode/8f627448-91f8-4992-8680-f39dfd495035/5aa33d6a-09a5-4b36-a97f-ad433c4ac494] Transcoder segment range: 0 - 34 (34)

I’m getting tons of these as well

[Req#63806/Transcode] Streaming Resource: Timing out session 0x1479bdc937a8:dda3343a-7327-4a30-89e5-6f9a7d06e5ec

Again, this is primarily only happening for FLAC. MP3 loads quickly and plays fine, however, scrubbing is a struggle for MP3 as well. The file isn’t skipping or restarting when attempting to scrub, however, most of the time it just doesn’t work. Sometimes I’ll get a spinning wheel for 30 or 40 seconds before the track actually moves to position.

3

Can you please provide server DEBUG log files (the ZIP file) which capture the start of and the first 30-40 seconds of Playback?

4

Hey @ChuckPa . Thanks for picking up my message. I’ve attached logs. I hope they’re helpful. Things seemed pretty smooth when I started listening today. But then, audio just dropped out in the middle of the song. The playhead continued to move and count, but no audio. I was also unable to advance to either the prev or next track or scrub the playhead. I couldn’t manually choose another track. Couldn’t really do anything. I downloaded the logs shortly after that happened.
Plex Media Server Logs_2024-10-19_17-18-08.zip (5.0 MB)
I had to go through a dance of disconnecting from the Sonos speaker and force closing and reopening the app 2 or 3 times before I could use Plexamp again.

5

Looking at the logs, I can see the ‘RINCON’ (sonos?) device playing as it pulls music blocks

I can see they are FLAC files.

I see in several different people playing simultaneously.

There is one thing I see which I don’t like and PMS didn’t like either.

Oct 19, 2024 07:11:19.689 [22513159703352] DEBUG - Request: didn’t get any data from 199.45.155.108:35368: Connection reset by peer

Followed by what I would raise as a security flag to you to change your Plex port.

Oct 19, 2024 07:11:30.593 [22513159703352] DEBUG - Request: [199.45.155.108:55460 (WAN)] PRI * (4 live) #262cde TLS Signed-in
Oct 19, 2024 07:11:30.593 [22513159703352] ERROR - Error parsing HTTP request: PRI * HTTP/2.0

SM

Oct 19, 2024 07:11:30.593 [22513159703352] DEBUG - Completed: [199.45.155.108:55460] 400 PRI * (4 live) #262cde TLS 0ms 265 bytes

Don’t know what it’s searching for but PMS denied it and carried on.

Did PMS stumble when this happened or did it give you issues later ?

Having a timestamp would be VERY helpful.

6

Thank you for that. My router does show some blocked incoming traffic around that time. I’ve closed the port and will move it tomorrow. However, the issue was later in the day. I don’t have an exact timestamp, but the issue was within a few minutes of me downloading the log. Logs end at 5:18 so I’d guess between 5:10 and 5:18. If that’s not narrow enough, I’ll pay closer attention tomorrow and send new logs.

7

The only thing which doesn’t make sense in this block is this:

Oct 19, 2024 17:10:06.185 [22512960781112] DEBUG - [Req#2721fa/ViewStateSync] Finished
Oct 19, 2024 17:10:07.256 [22512965786424] DEBUG - Request: [127.0.0.1:35260 (Loopback)] GET /identity (10 live) #272215 Signed-in
Oct 19, 2024 17:10:07.256 [22513159703352] DEBUG - Completed: [127.0.0.1:35260] 200 GET /identity (10 live) #272215 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:10:12.299 [22513016138552] DEBUG - Request: [127.0.0.1:58420 (Loopback)] GET /identity (10 live) #27221b Signed-in
Oct 19, 2024 17:10:12.299 [22513161812792] DEBUG - Completed: [127.0.0.1:58420] 200 GET /identity (10 live) #27221b 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:10:17.337 [22513016138552] DEBUG - Request: [127.0.0.1:58430 (Loopback)] GET /identity (8 live) #27221e Signed-in
Oct 19, 2024 17:10:17.337 [22513161812792] DEBUG - Completed: [127.0.0.1:58430] 200 GET /identity (8 live) #27221e 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:10:22.375 [22513016138552] DEBUG - Request: [127.0.0.1:56364 (Loopback)] GET /identity (7 live) #272223 Signed-in
Oct 19, 2024 17:10:22.375 [22513159703352] DEBUG - Completed: [127.0.0.1:56364] 200 GET /identity (7 live) #272223 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:10:27.420 [22513016138552] DEBUG - Request: [127.0.0.1:56374 (Loopback)] GET /identity (6 live) #272227 Signed-in
Oct 19, 2024 17:10:27.420 [22513161812792] DEBUG - Completed: [127.0.0.1:56374] 200 GET /identity (6 live) #272227 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:10:32.454 [22513016138552] DEBUG - Request: [127.0.0.1:34140 (Loopback)] GET /identity (6 live) #27222b Signed-in
Oct 19, 2024 17:10:32.454 [22513161812792] DEBUG - Completed: [127.0.0.1:34140] 200 GET /identity (6 live) #27222b 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:10:37.482 [22513016138552] DEBUG - Request: [127.0.0.1:34150 (Loopback)] GET /identity (6 live) #27222e Signed-in
Oct 19, 2024 17:10:37.482 [22513159703352] DEBUG - Completed: [127.0.0.1:34150] 200 GET /identity (6 live) #27222e 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:10:42.516 [22513016138552] DEBUG - Request: [127.0.0.1:56618 (Loopback)] GET /identity (6 live) #272231 Signed-in
Oct 19, 2024 17:10:42.516 [22513161812792] DEBUG - Completed: [127.0.0.1:56618] 200 GET /identity (6 live) #272231 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:10:47.550 [22513016138552] DEBUG - Request: [127.0.0.1:56628 (Loopback)] GET /identity (6 live) #272234 Signed-in
Oct 19, 2024 17:10:47.550 [22513161812792] DEBUG - Completed: [127.0.0.1:56628] 200 GET /identity (6 live) #272234 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:10:52.581 [22513016138552] DEBUG - Request: [127.0.0.1:37070 (Loopback)] GET /identity (6 live) #272237 Signed-in
Oct 19, 2024 17:10:52.581 [22513161812792] DEBUG - Completed: [127.0.0.1:37070] 200 GET /identity (6 live) #272237 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:10:57.612 [22513016138552] DEBUG - Request: [127.0.0.1:37086 (Loopback)] GET /identity (6 live) #27223a Signed-in
Oct 19, 2024 17:10:57.612 [22513159703352] DEBUG - Completed: [127.0.0.1:37086] 200 GET /identity (6 live) #27223a 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:02.647 [22513016138552] DEBUG - Request: [127.0.0.1:56768 (Loopback)] GET /identity (6 live) #27223d Signed-in
Oct 19, 2024 17:11:02.647 [22513161812792] DEBUG - Completed: [127.0.0.1:56768] 200 GET /identity (6 live) #27223d 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:07.676 [22513016138552] DEBUG - Request: [127.0.0.1:56772 (Loopback)] GET /identity (6 live) #272240 Signed-in
Oct 19, 2024 17:11:07.676 [22513159703352] DEBUG - Completed: [127.0.0.1:56772] 200 GET /identity (6 live) #272240 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:12.715 [22513016138552] DEBUG - Request: [127.0.0.1:52762 (Loopback)] GET /identity (6 live) #272243 Signed-in
Oct 19, 2024 17:11:12.715 [22513159703352] DEBUG - Completed: [127.0.0.1:52762] 200 GET /identity (6 live) #272243 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:17.755 [22513016138552] DEBUG - Request: [127.0.0.1:52776 (Loopback)] GET /identity (6 live) #272246 Signed-in
Oct 19, 2024 17:11:17.755 [22513161812792] DEBUG - Completed: [127.0.0.1:52776] 200 GET /identity (6 live) #272246 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:22.805 [22513016138552] DEBUG - Request: [127.0.0.1:36032 (Loopback)] GET /identity (6 live) #272249 Signed-in
Oct 19, 2024 17:11:22.805 [22513159703352] DEBUG - Completed: [127.0.0.1:36032] 200 GET /identity (6 live) #272249 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:27.835 [22513016138552] DEBUG - Request: [127.0.0.1:36044 (Loopback)] GET /identity (6 live) #27224c Signed-in
Oct 19, 2024 17:11:27.835 [22513161812792] DEBUG - Completed: [127.0.0.1:36044] 200 GET /identity (6 live) #27224c 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:32.868 [22513016138552] DEBUG - Request: [127.0.0.1:58030 (Loopback)] GET /identity (6 live) #27224f Signed-in
Oct 19, 2024 17:11:32.868 [22513161812792] DEBUG - Completed: [127.0.0.1:58030] 200 GET /identity (6 live) #27224f 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:37.897 [22513016138552] DEBUG - Request: [127.0.0.1:58036 (Loopback)] GET /identity (6 live) #272252 Signed-in
Oct 19, 2024 17:11:37.897 [22513161812792] DEBUG - Completed: [127.0.0.1:58036] 200 GET /identity (6 live) #272252 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:42.923 [22513016138552] DEBUG - Request: [127.0.0.1:39536 (Loopback)] GET /identity (6 live) #272255 Signed-in
Oct 19, 2024 17:11:42.923 [22513161812792] DEBUG - Completed: [127.0.0.1:39536] 200 GET /identity (6 live) #272255 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:47.956 [22513016138552] DEBUG - Request: [127.0.0.1:39548 (Loopback)] GET /identity (6 live) #272258 Signed-in
Oct 19, 2024 17:11:47.956 [22513159703352] DEBUG - Completed: [127.0.0.1:39548] 200 GET /identity (6 live) #272258 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:52.999 [22513016138552] DEBUG - Request: [127.0.0.1:58020 (Loopback)] GET /identity (6 live) #27225b Signed-in
Oct 19, 2024 17:11:52.999 [22513159703352] DEBUG - Completed: [127.0.0.1:58020] 200 GET /identity (6 live) #27225b 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:58.034 [22513016138552] DEBUG - Request: [127.0.0.1:58032 (Loopback)] GET /identity (6 live) #27225e Signed-in
Oct 19, 2024 17:11:58.034 [22513159703352] DEBUG - Completed: [127.0.0.1:58032] 200 GET /identity (6 live) #27225e 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:11:59.186 [22513016138552] DEBUG - Request: [54.170.120.91:20602 (WAN)] GET /identity (6 live) #272261 TLS Signed-in
Oct 19, 2024 17:11:59.186 [22513161812792] DEBUG - Completed: [54.170.120.91:20602] 200 GET /identity (6 live) #272261 TLS 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:12:03.072 [22513016138552] DEBUG - Request: [127.0.0.1:51414 (Loopback)] GET /identity (7 live) #272264 Signed-in
Oct 19, 2024 17:12:03.072 [22513159703352] DEBUG - Completed: [127.0.0.1:51414] 200 GET /identity (7 live) #272264 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:12:08.101 [22513016138552] DEBUG - Request: [127.0.0.1:51418 (Loopback)] GET /identity (7 live) #272266 Signed-in
Oct 19, 2024 17:12:08.101 [22513159703352] DEBUG - Completed: [127.0.0.1:51418] 200 GET /identity (7 live) #272266 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:12:13.135 [22513016138552] DEBUG - Request: [127.0.0.1:35062 (Loopback)] GET /identity (7 live) #272269 Signed-in
Oct 19, 2024 17:12:13.135 [22513159703352] DEBUG - Completed: [127.0.0.1:35062] 200 GET /identity (7 live) #272269 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:12:18.173 [22513016138552] DEBUG - Request: [127.0.0.1:35066 (Loopback)] GET /identity (7 live) #27226c Signed-in
Oct 19, 2024 17:12:18.173 [22513161812792] DEBUG - Completed: [127.0.0.1:35066] 200 GET /identity (7 live) #27226c 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:12:23.204 [22513016138552] DEBUG - Request: [127.0.0.1:54632 (Loopback)] GET /identity (6 live) #27226f Signed-in
Oct 19, 2024 17:12:23.204 [22513161812792] DEBUG - Completed: [127.0.0.1:54632] 200 GET /identity (6 live) #27226f 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:12:28.234 [22513016138552] DEBUG - Request: [127.0.0.1:54644 (Loopback)] GET /identity (6 live) #272273 Signed-in
Oct 19, 2024 17:12:28.234 [22513159703352] DEBUG - Completed: [127.0.0.1:54644] 200 GET /identity (6 live) #272273 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:12:33.265 [22513016138552] DEBUG - Request: [127.0.0.1:54970 (Loopback)] GET /identity (6 live) #272276 Signed-in
Oct 19, 2024 17:12:33.265 [22513159703352] DEBUG - Completed: [127.0.0.1:54970] 200 GET /identity (6 live) #272276 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:12:38.297 [22513016138552] DEBUG - Request: [127.0.0.1:54982 (Loopback)] GET /identity (6 live) #272279 Signed-in
Oct 19, 2024 17:12:38.297 [22513159703352] DEBUG - Completed: [127.0.0.1:54982] 200 GET /identity (6 live) #272279 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:12:43.360 [22513016138552] DEBUG - Request: [127.0.0.1:49506 (Loopback)] GET /identity (6 live) #27227c Signed-in
Oct 19, 2024 17:12:43.360 [22513161812792] DEBUG - Completed: [127.0.0.1:49506] 200 GET /identity (6 live) #27227c 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:12:48.395 [22513016138552] DEBUG - Request: [127.0.0.1:49512 (Loopback)] GET /identity (6 live) #27227f Signed-in
Oct 19, 2024 17:12:48.395 [22513161812792] DEBUG - Completed: [127.0.0.1:49512] 200 GET /identity (6 live) #27227f 0ms 417 bytes (pipelined: 1)
Oct 19, 2024 17:12:53.439 [22513016138552] DEBUG - Request: [127.0.0.1:45370 (Loopback)] GET /identity (6 live) #272282 Signed-in
Oct 19, 2024 17:12:53.439 [22513161812792] DEBUG - Completed: [127.0.0.1:45370] 200 GET /identity (6 live) #272282 0ms 417 bytes (pipelined: 1)

Something is asking if the server is claimed. Something running on the host itself.

Does this make any sense?

8

Not really. I run a Windows VM on the server and the Plexamp app on the VM is one of the primary ways I listen to my music. However, I mostly initiate from my iPhone and I’m 95% certain I did this time as well. Maybe Plex or Plexamp in Windows is just constantly checking if my server is claimed even if it’s not the source of the music. My only other thought that sorta makes sense is that I’m relatively new to Unraid and getting Unraid running has been one of the most tedious and mind-numbing experiences of my life. I’ve run into countless nonsensical issues for every step of the process. This is starting to seem like another random Unraid issue. I’m starting to think if I simply move my PMS to a different platform my problems will go away.

9

I’ve shut down all other services and VMs. The Windows VM has it’s own networking and IP which makes sense so my previous reply in that regard is null and void. The only service running on the host currently is PMS and the console is currently being flooded with those messages. It’s running in docker using the official Plex image.

10

To confirm:

Your UNRAID host is running only 1 service – The Plex, inc Docker one ?

11

Well typically I run a few others. But I’ve turned them all off this morning. I turned off VMs as well. It is also the only container I ever run with host networking and I don’t run any other containers that should be interacting with Plex. When I sent that message only PMS was running and I was still seeing the same repeated messages in the console.

12

Does Unraid have the kernel update for that machine yet?

Asking because the i9-149xx should minimally be running a 6.8 kernel for the hardware.

I have an “Older” AlderLake (i9-12900) and it’s on 6.8 kernel.

13

This is a normal message whenever transcoder is running.

I’m very surprised it’s showing up on your console.
It should be confined to your logs

14

Newest version of Unraid is on 6.1.103.

Could the transcoder messages be part of my issue though? They shouldn’t be transcoding and dashboard says “Direct Play”.

15

the plot thinkens …lol

The player always controls the bitrates and whether/not there is a transcode.

player app setting change?

16

Well…my player is Sonos… they’ve been having hard times to say the least since they released a completely revamped app in May. Honestly, I was basically assuming them to be at fault, but I haven’t experienced the same issues when the files are accessed directly by Sonos over SMB. It just seems like something in the pipe between the 2 is broken.

On a related note, there’s chatter on the forums about a Plexamp multi-zone solution. Even saw a note directly from Elan. Any news there?

17

Just happened again. Precisely 4:50pm. Audio dropped on song and it pretended to play for a few more seconds. Then Plex just skipped through all remaining tracks and started playing another album.

Plex Media Server Logs_2024-10-21_16-52-06.zip (3.2 MB)

18

Thanks, I see it.

Oct 21, 2024 16:49:48.705 [23294721448760] DEBUG - Completed: [127.0.0.1:41834] 200 GET /identity (5 live) #af16 0ms 417 bytes (pipelined: 1)
Oct 21, 2024 16:49:48.918 [23294693022520] DEBUG - Request: [10.23.15.100:36944 (Allowed Network (WAN))] GET /statistics/bandwidth?timespan=6 (4 live) #af1e TLS GZIP Signed-in Token (bigwallymonster) (fedora)
Oct 21, 2024 16:49:48.919 [23294721448760] DEBUG - Completed: [10.23.15.100:36944] 200 GET /statistics/bandwidth?timespan=6 (4 live) #af1e TLS GZIP 0ms 1567 bytes (pipelined: 4)
Oct 21, 2024 16:49:49.926 [23294615067448] DEBUG - Request: [10.23.15.100:36944 (Allowed Network (WAN))] GET /statistics/bandwidth?timespan=6 (4 live) #af22 TLS GZIP Signed-in Token (bigwallymonster) (fedora)
Oct 21, 2024 16:49:49.927 [23294719339320] DEBUG - Completed: [10.23.15.100:36944] 200 GET /statistics/bandwidth?timespan=6 (4 live) #af22 TLS GZIP 0ms 1571 bytes (pipelined: 5)
Oct 21, 2024 16:49:50.094 [23294683401016] DEBUG - [Req#abcf] Streaming Resource: Timing out session 0x152fb9c911c8:token=xxxxxxxxxxxxxxxxxxxx
Oct 21, 2024 16:49:50.094 [23294683401016] DEBUG - [Req#abcf] Streaming Resource: Terminated session 0x152fb9c911c8:token=xxxxxxxxxxxxxxxxxxxx with reason Client stopped playback.
Oct 21, 2024 16:49:50.094 [23294683401016] DEBUG - [Req#abcf] Streaming Resource: Removing session 0x152fb9c911c8:token=xxxxxxxxxxxxxxxxxxxx
Oct 21, 2024 16:49:50.919 [23294615067448] DEBUG - Request: [10.23.15.100:36944 (Allowed Network (WAN))] GET /statistics/bandwidth?timespan=6 (4 live) #af23 TLS GZIP Signed-in Token (bigwallymonster) (fedora)
Oct 21, 2024 16:49:50.920 [23294721448760] DEBUG - Completed: [10.23.15.100:36944] 200 GET /statistics/bandwidth?timespan=6 (4 live) #af23 TLS GZIP 0ms 1576 bytes (pipelined: 6)
Oct 21, 2024 16:49:50.951 [23294621395768] DEBUG - Request: [10.23.15.100:36944 (Allowed Network (WAN))] GET /statistics/resources?timespan=6 (4 live) #af24 TLS GZIP Signed-in Token (bigwallymonster) (fedora)
Oct 21, 2024 16:49:50.951 [23294719339320] DEBUG - Completed: [10.23.15.100:36944] 200 GET /statistics/resources?timespan=6 (4 live) #af24 TLS GZIP 0ms 850 bytes (pipelined: 7)
Oct 21, 2024 16:49:51.926 [23294621395768] DEBUG - Request: [10.23.15.100:36944 (Allowed Network (WAN))] GET /statistics/bandwidth?timespan=6 (4 live) #af25 TLS GZIP Signed-in Token (bigwallymonster) (fedora)
Oct 21, 2024 16:49:51.927 [23294721448760] DEBUG - Completed: [10.23.15.100:36944] 200 GET /statistics/bandwidth?timespan=6 (4 live) #af25 TLS GZIP 0ms 1581 bytes (pipelined: 8)
Oct 21, 2024 16:49:52.921 [23294621395768] DEBUG - Request: [10.23.15.100:36944 (Allowed Network (WAN))] GET /statistics/bandwidth?timespan=6 (4 live) #af26 TLS GZIP Signed-in Token (bigwallymonster) (fedora)
Oct 21, 2024 16:49:52.922 [23294719339320] DEBUG - Completed: [10.23.15.100:36944] 200 GET /statistics/bandwidth?timespan=6 (4 live) #af26 TLS GZIP 0ms 1585 bytes (pipelined: 9)
Oct 21, 2024 16:49:53.735 [23294693022520] DEBUG - Request: [127.0.0.1:39732 (Loopback)] GET /identity (5 live) #af1f Signed-in
Oct 21, 2024 16:49:53.735 [23294719339320] DEBUG - Completed: [127.0.0.1:39732] 200 GET /identity (5 live) #af1f 0ms 417 bytes (pipelined: 1)

Here you can see the client stopped the playback.
I have no idea why at this point.

Are you able to get the Sonos logs?

From what I’m able to determine, Plex Remote Access must be working for Sonos to talk to Plex

I do have a question.
– Your primary LAN network is 192.168.1.x
– These playbacks are coming from 10.23.15.x. (Labeled WAN)

Is there a specific requirement to have the two subnets ?
( I see a 10.0.0.1 bridge adapter defined )

19

Primary is 10. Windows VM is on VLAN simply for Unraid/experimenting/learning reasons. In this case is the client Sonos or Plexamp? I’ll look into Sonos logs, but I’m not aware that users can access anything that’s meaningful to people other than Sonos employees. If I try to contact Sonos I’ll most certainly just be told the issue is my network or Plex. Also, Fedora is my laptop and that’s definitely the laptop’s IP. I WAS NOT listening on my laptop. I never listen on my laptop. I was listening to Plexamp on my phone in the kitchen. I have Plex installed on laptop strictly for admin, testing, dashboard, etc. And Plexamp isn’t even installed. Are my devices competing with each other somehow? Like Plex doesn’t actually know which device is playing and that’s causing issues? Does that even make sense? It does not make sense that fedora is listed as the client. I’m only seeing a snippet here. Do you see any other 10.xx IPs (my iPhone)? Exactly which file in the logs are you seeing this data?

20

This is what Plex sees.

It thinks it’s on a 192.168.1.42 IP addr

Oct 21, 2024 13:34:37.554 [23294816311952] DEBUG - NetworkInterface: Notified of network changed (force=0)
Oct 21, 2024 13:34:37.554 [23294665276216] DEBUG - NetworkInterface: Watching for changes on the interfaces.
Oct 21, 2024 13:34:37.554 [23294816311952] DEBUG - Detected primary interface: 192.168.1.42
Oct 21, 2024 13:34:37.554 [23294816311952] DEBUG - Network interfaces:
Oct 21, 2024 13:34:37.554 [23294816311952] DEBUG -  * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Oct 21, 2024 13:34:37.554 [23294816311952] DEBUG -  * 5 br0 (192.168.1.42) (D8-43-AE-15-0E-0F) (loopback: 0)
Oct 21, 2024 13:34:37.554 [23294816311952] DEBUG -  * 7 br-119ec38a81cc (10.0.0.1) (02-42-ED-9D-32-D7) (loopback: 0)
Oct 21, 2024 13:34:37.554 [23294816311952] DEBUG -  * 8 br-27c122cdb886 (192.168.176.1) (02-42-DC-EC-80-DD) (loopback: 0)
Oct 21, 2024 13:34:37.554 [23294816311952] DEBUG -  * 9 br-89c6595442fe (192.168.144.1) (02-42-53-28-B7-6A) (loopback: 0)
Oct 21, 2024 13:34:37.554 [23294816311952] DEBUG - Creating NetworkServices singleton.

The only 10.x.x.x I see is this (your iphone?)

Oct 21, 2024 13:34:49.844 [23294673713976] DEBUG - Request: [10.23.15.237:62691 (Allowed Network (WAN))] GET /media/providers?includePreferences=1 (3 live) #36 TLS GZIP Signed-in Token (bigwallymonster) (iPhone)
Oct 21, 2024 13:34:49.857 [23294633696056] DEBUG - Request: [10.23.15.237:62705 (Allowed Network (WAN))] GET /hubs/sections/3?count=6&includeExternalMetadata=1&includeMyMixes=1&includeAnniversaryReleases=1&excludeElements=Similar,Mood&includeLibraryPlaylists=1&includeStations=1&includeStationDirectories=1&excludeFields=summary&includeFields=thumbBlurHash (4 live) #35 TLS GZIP Signed-in Token (bigwallymonster) (iPhone)

Notice PMS says “WAN” ??? PMS thinks it’s remote / knows it’s on a different subnet.

You might want to go into network settings: “Treat WAN as LAN”.

I think this addressing issue is the heart of the problem.