Plex on Hisense using vidaa app?

Plex Media Server
,
1

Hi folks,

I’m scratching my head at the moment, so if anyone can see something of significance in the logs I would really appreciate the help.

I have a Synology DS224+ and I have set up the holy trinity running through docker. Prior to the new app update I was running the plex app on my iPhone and air playing to my Hisense tv without issue. Since the update broke plex app airplay on my iPhone (it doesn’t find devices to cast to through the app and when I try just using airplay on the phone it won’t connect), I’ve been trying to use the app on my Hisense (VIDAA plex app 5.19.0) and the videos just keep buffering after a few seconds.

Both the TV and the NAS are hardwired to ethernet (though I did try switching the TV to Wi-Fi in case it was a limitation of the ethernet port on the TV). I can use the app on my iPhone/iPad and watch from my server via Wi-Fi just fine, the problems present when I try to use the built-in app on the tv and also when I try to use Infuse to stream to the tv.

I’ve only recently dipped my toes into the whole NAS/Docker/Plex setup, so if I am missing any important information please let me know. I scoured reddit before I purchased the DS224+ to make sure it could do transcoding etc so I don’t believe it’s a limitation of the NAS itself, especially when I can stream on my apple devices without issue.

If you have made it this far, I appreciate you sticking with me and if you have any tips/advice I would really really reaaaaallllyyy appreciate that too.

Thank you!

EDIT: I didn’t think to add the plex app to my PS5 and see if that works without buffering, which it does. I am almost certain the issue is with the VIDAA plex app.

Still wondering if anyone has encountered a workaround to get things back up and running on VIDAA though. I really like the idea of having all of my apps on the TV so that I don’t have to run anything else or switch sources.

Server Version#: 1.41.7.9799
Player Version#:5.91.0 (Plex for Vidaa)
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
Plex Media Server Logs_2025-05-23_19-41-19.zip (221.5 KB)

2

Looking at your logs it’s failing to establish a secure connection (I’m not an expert though.) You can check on the web gui [Server Name] -> Settings -> Network and set it to preferred and see if it makes a difference. Also is your docker container “network mode” set to HOST?

May 23, 2025 19:40:05.733 [140251262663480] INFO - [Req#db] [Plex for VIDAA] [PtePartz:mzrxzv1h7fccvw9qsi6pzmsf] VIDAA_getAdsParameters_V2 callback result,{"resultCode":1,"errorCode":"appId invalid"}
May 23, 2025 19:40:05.733 [140251262663480] WARN - [Req#db] [Plex for VIDAA] [PtePartz:mzrxzv1h7fccvw9qsi6pzmsf] [getAdParameters] Error getting advertising parameters: appId invalid
May 23, 2025 19:40:05.734 [140251262663480] ERROR - [Req#db] [Plex for VIDAA] [PtePartz:mzrxzv1h7fccvw9qsi6pzmsf] [Unhandled Rejection]: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS. 
Error: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
May 23, 2025 19:40:11.000 [140251262663480] ERROR - [Req#ed] [Plex for VIDAA] [PtePartz:mzrxzv1h7fccvw9qsi6pzmsf] [Unhandled Rejection]: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.

Did a search and it looks like it might be common to the app with no fix:
https://forums.plex.tv/search?q=vidaa%20app%20order%3Alatest

3

Thank you for taking the time to respond to this :slight_smile:

I think those logs was when I was troubleshooting with various suggestions on reddit. I changed the connection from allow insecure on local to always on the VIDAA app. Preferred is set in the server and I have not changed it at all.

I am not sure about the docker network mode. I used the TRaSH guide to setup on a synology NAS, the extent of my meddling was to put all the required information into the docker compose.

On an interesting note, it seems files that are under 1GB in size play for much longer without buffering.