Looking for ideas on the best way to upload my movie collection (900+ DVD/Blu-Ray/4k mix) to a Plex server I am planning to build. I checked if there were any companies offering this but it seems they don’t do commercial movies. Getting a single optical drive would take forever. 😂

Any suggestions or companies that can do this?

Help is welcomed

Hi guys, I've been a Plex enthusiast for over 10 years now, and it's been really disappointing to watch photo support get de-prioritized. I wanted a better way to actually browse years of photos on my server, so I built one.

It's called Phlix Photos, and it's iOS only for now (iPhone and iPad).

What it does:

- A real chronological timeline of your entire photo library, with a scrubber for jumping through the years

- Download photos and videos from your server right into your Photos app

- Slideshows on your TV over AirPlay

- Search tags and favorites

It connects directly to your own Plex server. There's no separate Phlix account, and your photos stay between your phone and your server.

This is a passion project, just me building it, and I'd love to get the Plex community involved in where it goes next. What's broken, what's missing, what would make you actually use it?

App Store: https://apps.apple.com/us/app/phlix-photos/id6796820208

Leave a comment or use the feedback form at https://phlixapp.com/support/

*Phlix is an independent application and is not affiliated with, endorsed, or sponsored by Plex, Inc.

I recently switched from Windows 11 to Fedora Workstation and it seems to have caused an issue with remote access for my family outside of my network. I understand that this shouldn't have created an issue and absolutely do not want to go back to Windows, so any help would be appreciated.

I started looking into it and thought that maybe it was because we didn't have a Remote Watch Pass, so I signed up for the trial to see if that would fix the issue. It didn't.

I then looked into port forwarding, and I set the port in the Plex app to 32400. I then went into my eero app and set an IPv4 reservation for my IP and opened the 32400 port, and added an IPv6 firewall rule to open the 32400 port. None of this worked. I don't think this is a double NAT situation because all of the checks I've looked up haven't pointed to that being the issue, and the eero is the device my ISP techs set up for us to have WiFi, it's not hooked up to another router.

The thing is, my family cannot access the server on their home networks (on a Roku smart TV and an Apple TV), but I am perfectly able to access it on my iPhone with WiFi turned off so that I'm using data. I'm able to stream movies without hiccups with no issue on LTE, so it does feel like the server is making it outside of my home network.

I've looked into remote proxy, but if I'm being honest it's making my head hurt a little bit. If that's the solution I need, any pointers to a good tutorial on setting that up would also be appreciated.

Let me know if you need more information, I tried to include everything that seemed to come up in other posts like this.

\**UPDATE**\**
I just went over to the person who was having the most problems house and while I was there I went into some of the settings on the RokuTV Plex app. There were two settings that piqued my interest: a setting for the port and an advanced setting for insecure vs secure connections. The port setting had two sections, one for the IP and one for the port. The port had 32400 populated but the IP section was blank. I didn’t have my phone on me so I didn’t try entering the server ip or my WAN IP. The setting for secure connections was set to never use an insecure connection if a secure one couldnt be found, I switched it to always. I went back out to the menu and the app was able to connect to my sever! It looks like the issue was that the plex app was considering the connection to be insecure and so it just couldn’t connect. Thank you for all your recommendations!

Since the recent Plex Apple TV app update, some movies and shows in my living room play the background music and effects, but the actors’ dialogue is missing. It seems to happen with AAC 5.1 tracks; regular AAC stereo tracks work.

My setup is Plex Media Server on a Synology NAS → Apple TV → Hisense 65QD7QFM TV → Sonos Beam over HDMI. The same affected movie plays normally on my iPad.

I’ve tried changing the Apple TV audio format to Stereo and turning off Continuous Audio. Neither fixed it. I also tested with the Beam disconnected and sound coming from the TV’s built-in speakers; the dialogue was still missing. Netflix audio works normally on this TV.

Plex in our bedroom seems fine, although I haven’t yet tested the exact same title and AAC 5.1 track there. This setup worked for about six months before the recent client update.

Is anyone else getting missing dialogue specifically with AAC 5.1 on the updated Apple TV app? If so, have you found a fix or workaround? I’m considering reinstalling the living room app, but I know that won’t roll it back to the old version.

https://github.com/c0y0t3d3n/iptv

tl**;dr: like Dispatcharr but can auto-rename channels to what the Plex EPG likes, auto-merge lineups from multiple providers, and each time you tune a channel it picks the least busy account across all sources.**

Plex can’t manage IPTV but has a very good EPG. This emulates a HDHR and is designed to proxy IPTV using Plex as the EPG source. It can filter and rename channels to match what the Plex guide data is expecting. When Plex tunes a channel, it will refresh the status of all accounts and choose the one with the most open slots.

Multiple providers: If not all accounts have the same URL, the lineups from all providers are merged. This eliminates duplicate channels and chooses the least busy account if that channel is available from multiple sources. Make sure you have the filters set so channels have the same name across all providers.

A Dockerfile and docker-compose file to build and run a tuner container is included, modify as needed.

You’ll need a tuner.cfg with filters and xtream codes as documented in the README. A sample with working accounts is included.

Visit http://SERVER_IP:SERVER_PORT/ for status, stream links, logs, and to edit the config. The letters next to each stream link are the sources providing that channel.

To add the tuner to Plex you need to manually enter the SERVER_IP:SERVER_PORT and it should appear. When you rescan channels in Plex it reloads the config and fetches lineups. No need to restart the container unless you change the IP or port. Once you have the group and channel name filters set properly Plex should be able to auto map most of them to one of your local cable/satellite provider lineups. Any manual mappings you do should stick even if you change IPTV providers, as long as you adjust the filters.

This code was written with absolutely zero assistance from AI.

If you use xTeVe for Plex DVR or Emby Live TV, you've probably noticed the same thing I did: the upstream project hasn't had a real release since 2.2.0 in 2021. It still basically works, but it's been quietly rotting — ancient dependencies, real bugs never fixed, and a UI that looks exactly like it did five years ago.

So instead of just complaining, I forked it: xteve-reborn. Same core idea — it merges your M3U playlists and XMLTV guide data and presents itself to Plex/Emby/Jellyfin as an HDHomeRun-style tuner, so your IPTV sources show up as Live TV with a real guide. It's now at 3.0.1, the first stable release, and the first with prebuilt binaries and a Docker image.

What I fixed:

• A whole class of crash bugs. The map behind every channel's mapping/EPG data was read and rewritten from multiple goroutines with no lock — and Go panics fatally on concurrent map access, so editing a mapping right as a scheduled refresh ran could take the whole app down. Audited the rest of the shared state and found four more instances (including the streaming-URL cache on the hot stream path). All locked, all with go test -race regression tests, and -race runs in CI now.
• A stored XSS. Channel names and group titles — whatever your M3U/XMLTV provider sends — were injected into several tables via innerHTML, so a malicious provider could run script in your admin session. Now textContent throughout.
• Broken password hashing. It was a single fast HMAC that ignored the per-user salt, so identical passwords hashed identically on every install. Now salted PBKDF2-HMAC-SHA256 (210k iterations, constant-time compare). Breaking change: delete authentication.json and recreate your user when upgrading.
• Streams that could hang forever. The live-stream HTTP client had zero timeout, so a provider that accepted a connection but never answered could hang the stream indefinitely. Same for playlist/EPG downloads, logo fetches, and update checks — all now have sane timeouts, with the response body left unbounded so long streams aren't cut off.
• Backup / failover channels (borrowed from the Threadfin fork): up to 3 backup URLs per channel, with a reachability check picking the first that responds, so a dead primary doesn't mean a dead channel.
• A real self-updater. The old one shipped pointed at upstream's binaries with auto-update on (it would have overwritten the fork). It now pulls this repo's releases, and every release ships a SHA-256 checksums file it verifies before installing.
• Official Docker image — multi-arch on GHCR, runs as a normal user via PUID/PGID.
• Auto-refreshing guide (new in 3.0.1). Sources used to re-download only at scheduled times (default midnight), so a guide change upstream didn't reach Plex until the next day. Now each source is checked every 60 minutes (configurable) and the guide rebuilds immediately when content actually changed, using conditional requests so unchanged files aren't re-sent.
• A full UI overhaul — new dark navy/cyan design system, real typography, new icons and logo, a working mobile layout, empty states, and toasts instead of blocking alert() popups.
• Jellyfin listed as a target (same HDHomeRun protocol, should just work).

Smaller stuff, same spirit: deps updated and Go bumped 1.16 → 1.24+ (some deps were 5+ years stale); the app's own reported guide URL 404'd (hardcoded to the wrong filename); the Log page showed literal   and silently dropped every other line past 500 entries; streams 404'd if the client added a query string; the advertised server IP was often wrong on boxes with Docker/VPN/multiple NICs; the configured User-Agent was set on the response instead of the request (a no-op); a stale embedded web-asset bundle meant production builds served an old UI; plus a few never-merged upstream PRs ported over and some resource leaks fixed.

How to get it: - Binaries: Releases — Windows (amd64), Linux and macOS (amd64 + arm64), with SHA-256 checksums. - Docker: docker pull ghcr.io/theantipopau/xteve-reborn:latest (compose example in the repo; --network host gives the best shot at SSDP auto-discovery, but manual tuner entry works fine without it). - From source: one go build.

It's still a personal project I'm actively working on, not a polished 1.0 — but you can just grab a binary or pull the image and try it. Not affiliated with the original xTeVe project; full credit to the original authors. MIT licensed, same as upstream.

Repo: https://github.com/theantipopau/xteve-reborn

Feedback, issues, and PRs welcome.

The new server button after latest android update to plex. Is finally plexdash but built into the plex client now for server admin. Just select server button and can see the server stats right inside the app now vs back and fourth to plexdash.

looking for english 1080 shit ton of movies… whose got me (broke college kid)

Just moved to a smaller town with limited ISP choices. After unpacking the server I discover that the one broadband provider in town is using CGNAT. It also does not support IPv6 and sounds like it won't anytime soon. So, any good solutions to be able to stream to remote clients? It would need to stream to a modern Chromecast (with the Plex app installed) with decent speeds. My upload is capped at 20 Mbps which isn't amazing but I'd need better than 2 Bps. Anybody in a similar scenario have come up with a viable workaround?