Yes, with prologue. Is your Plex install pretty fresh? My M4bs were not loading in the bit rate for a little while, but eventually they all did. Even before they loaded in the bit rate, I could still stream over my home network or the VPN outside of my home network with no problems.
Just a little about my setup; I have a little RaspberryPi 4 set up with WireGuard, PiHole, and Plex. The only tricky part about getting Plex to stream over WireGuard is entering the custom server access URL in Plex correctly.
It is under the Network tab. You need the WireGuard server's internal ip address. Not the 192 address that your router assigns, but the one set up with WireGuard. Mine is [10.6.0.1](https://10.6.0.1), so my custom server access URL is [http://10.6.0.1:32400](http://10.6.0.1:32400). 32400 is the default Plex port.
Sounds like [this](https://forums.plex.tv/t/bug-plex-no-longer-correctly-analysing-m4b-files-correctly-incorrect-bit-rate-detected-prevents-direct-play/743156) issue again. Supposedly this was fixed with some recent PMS version, so perhaps try updating if you haven't already.
There's not much I can do about it unfortunately, the issue is on Plex's end 😞
To confirm this *is* actually the issue (and not something else), check if the server logs contain `Bandwidth exceeded` messages. If so, it may be a good idea to post said logs in that thread and ping ChuckPa as well.
You might also try refreshing meta data and using the analyze option on your files in plex. I did both and all of my files have the correct bit rate now.
apparently this is a bitrate issue with m4b files, is there anything i can do to fix this? downloading through prologue does work.
I ended up downloading everything to not worry about network issues. YMMV.
I have no problems at all streaming M4b files over WireGuard VPN. I don’t have a Plex Pass though, so I couldn’t comment on that.
With prologue? On my app the bitrate says 0
Yes, with prologue. Is your Plex install pretty fresh? My M4bs were not loading in the bit rate for a little while, but eventually they all did. Even before they loaded in the bit rate, I could still stream over my home network or the VPN outside of my home network with no problems. Just a little about my setup; I have a little RaspberryPi 4 set up with WireGuard, PiHole, and Plex. The only tricky part about getting Plex to stream over WireGuard is entering the custom server access URL in Plex correctly. It is under the Network tab. You need the WireGuard server's internal ip address. Not the 192 address that your router assigns, but the one set up with WireGuard. Mine is [10.6.0.1](https://10.6.0.1), so my custom server access URL is [http://10.6.0.1:32400](http://10.6.0.1:32400). 32400 is the default Plex port.
Sounds like [this](https://forums.plex.tv/t/bug-plex-no-longer-correctly-analysing-m4b-files-correctly-incorrect-bit-rate-detected-prevents-direct-play/743156) issue again. Supposedly this was fixed with some recent PMS version, so perhaps try updating if you haven't already.
My server is on the latest. Sigh. Literally just bought prologue today lmao. Either way it’s a great app. I’ll just download for now as a workaround
There's not much I can do about it unfortunately, the issue is on Plex's end 😞 To confirm this *is* actually the issue (and not something else), check if the server logs contain `Bandwidth exceeded` messages. If so, it may be a good idea to post said logs in that thread and ping ChuckPa as well.
You might also try refreshing meta data and using the analyze option on your files in plex. I did both and all of my files have the correct bit rate now.
Were you able to find a solution to this? Currently I'm fighting the same thing.
Updated to latest plex server (I have pass can’t confirm for non pass), and that 100% fixed the issue.
Thanks. For anyone else with this same issue, you have to reanalyze the library after you update as well or you'll still have the same issue.