# IPv6 Failure **URL:** \ **Category:** Plex Media Server\ **Tags:** server-linux\ **Created:** [March 25, 2023, 3:44am UTC](https://forums.plex.tv/t/ipv6-failure/835620 "2023-03-25T03:44:58Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![snack176](https://avatars.discourse-cdn.com/v4/letter/s/f9ae1b/32.png) [@snack176](https://forums.plex.tv/u/snack176)\ **Post date:** [March 25, 2023, 3:44am UTC](https://forums.plex.tv/t/ipv6-failure/835620/1 "2023-03-25T03:44:58Z")
Adding IPv6 CDIR Blocks in LAN networks like: fe80::/64 and 2403:5800:7800:2c00::/64 is a total failure. Plex cannot parse the IPv6 blocks as it does for IPv4 so we have no way of telling plex to treat our IPv6 devices all on the same LAN as a LAN! Server Version#: Latest Plex Pass Beta Mar 25, 2023 14:28:40.726 [0x7f9da4e0c8] ERROR - Error parsing allowedNetworks ‘fe80::64’: Invalid argument Mar 25, 2023 14:28:40.726 [0x7f9da4e0c8] ERROR - Error parsing allowedNetworks ‘2403:5800:7800:2c00::64’: Invalid argument ---
**Author:** ![anon5074910](https://avatars.discourse-cdn.com/v4/letter/a/db5fbb/32.png) [@anon5074910](https://forums.plex.tv/u/anon5074910)\ **Post date:** [March 25, 2023, 10:45am UTC](https://forums.plex.tv/t/ipv6-failure/835620/2 "2023-03-25T10:45:43Z")
While this may not be your issue, one thing to check is that in the `List of IP addresses and networks that are allowed without auth` that you have no spaces in the value you entered into that field. `192.168.1.4,192.168.1.8` is good but `192.168.1.4, 192.168.1.8` would be bad. I’ve seen that cause this error in the past. If you believe you have right value could you provide a screenshot of what you have so we can review. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [April 3, 2023, 10:44pm UTC](https://forums.plex.tv/t/ipv6-failure/835620/3 "2023-04-03T22:44:13Z")
> [@snack176](#): > > Adding IPv6 CDIR Blocks in LAN networks like: fe80::/64 and 2403:5800:7800:2c00::/64 is a total failure. Plex cannot parse the IPv6 blocks as it does for IPv4 so we have no way of telling plex to treat our IPv6 devices all on the same LAN as a LAN! This is a known issue (#14234) which I raised with Engineering today in our meeting. Current status: 1. Those fields were written for IPv4 only. 2. Having reviewed my bug report, Engineering has agreed to fix it. ( Add IPv6 support ) 3. I don’t know when it’s going to be fixed but do hope soon (there are a couple higher priority issues to resolve first ). 4. I’ve shared the issue number so you can follow the Release Announcements and know when it is resolved. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [April 7, 2023, 11:10pm UTC](https://forums.plex.tv/t/ipv6-failure/835620/4 "2023-04-07T23:10:01Z")
@snack176 @anon5074910 This issue is resolved. I’ll be testing it in as soon as engineering gives us a new binary (possibly the upcoming release) ---
**Author:** ![ulbador](https://avatars.discourse-cdn.com/v4/letter/u/59ef9b/32.png) [@ulbador](https://forums.plex.tv/u/ulbador)\ **Post date:** [April 12, 2023, 3:57am UTC](https://forums.plex.tv/t/ipv6-failure/835620/5 "2023-04-12T03:57:28Z")
> 1. Those fields were written for IPv4 only. I’m curious about this. This was never the case before. I’ve been primarily accessing plex over IPv6, with these fields populated, for a long long long time now. This just became an issue recently. Edit: Nevermind. This is just a flat out regression as IPv4 doesn’t work either ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [April 12, 2023, 5:06am UTC](https://forums.plex.tv/t/ipv6-failure/835620/6 "2023-04-12T05:06:39Z")
> [@ulbador](#): > > Edit: Nevermind. This is just a flat out regression as IPv4 doesn’t work either Show me please? LAN networks operates as it should in all I’ve tested. ---
**Author:** ![ulbador](https://avatars.discourse-cdn.com/v4/letter/u/59ef9b/32.png) [@ulbador](https://forums.plex.tv/u/ulbador)\ **Post date:** [April 12, 2023, 1:39pm UTC](https://forums.plex.tv/t/ipv6-failure/835620/7 "2023-04-12T13:39:53Z")
[[Album] imgur.com ![](https://i.imgur.com/3OUjLWu.png?fb "imgur.com") ](https://imgur.com/a/LxCop3G) It does seem to work just by IP though, This is all something that has worked for 4+ years and just recently broke ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [April 12, 2023, 6:24pm UTC](https://forums.plex.tv/t/ipv6-failure/835620/8 "2023-04-12T18:24:30Z")
What am I looking at here? [![](https://i.imgur.com/3OUjLWu.png?fb) ](https://i.imgur.com/3OUjLWu.png?fb) I was expecting to see the value you entered for LAN Networks. ---
**Author:** ![ulbador](https://avatars.discourse-cdn.com/v4/letter/u/59ef9b/32.png) [@ulbador](https://forums.plex.tv/u/ulbador)\ **Post date:** [April 13, 2023, 3:26am UTC](https://forums.plex.tv/t/ipv6-failure/835620/9 "2023-04-13T03:26:49Z")
I posted an album. The preview butchered it ![image](https://global.discourse-cdn.com/plex/original/4X/f/9/2/f92f12688ad4ed9bea234d11cdd8b908cea367ce.jpeg) ---
**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\ **Post date:** [July 12, 2023, 3:27am UTC](https://forums.plex.tv/t/ipv6-failure/835620/10 "2023-07-12T03:27:24Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.