publish server via IPv6


#1

Dear plex community,

 

Ive been running into some trouble with plex media server or myplex since 2 months, as some german ISPs switched to DS-Lite (a.k.a. Dual Stack lite with IPv4 over IPv6). This means myplex cant talk to its servers as I guess it is not running via IPv6 yet. Can anyone confirm if myplex runs or doesnt run over IPv6 right now? I have no chance to connect via ipv4 in the near future and as I am a plexpass member sometimes I cant sync content because it needs to connect to myplex, it at least says so. I sure know you have better things to do but as IPv6 is coming for all of us (more or less) one should consider this anyway.

 

Regards,

 

Jan


#2

If you go into plex/web media manager

Settings/Network/Show Advanced Settings

There is a checkbox for "Enable Server Support for IPV6"


#3

I have no idea why I havent seen this before. I was looking through the server settings 2 days ago to make this possible and I didnt find it. Ill check it out as soon as Im home, thanks mate


#4

Im still not able to publish it. Is this meant so its not trying to publish it via ipv4 also? Its because I still do have a IPv4 adress, its just completely NATed, so it wont reach me at all. Any ideas ?


#5

heres the important stuff of the server log : 

Mar 26, 2013 09:37:24 [0xb0aa9000] DEBUG -  * ManualPortMappingMode => 0
Mar 26, 2013 09:37:24 [0xb0aa9000] DEBUG - MyPlex: Setting manual port mode to 0.
Mar 26, 2013 09:37:24 [0xb0aa9000] DEBUG - NAT: Setting manual port mode: 0
Mar 26, 2013 09:37:24 [0xb0aa9000] DEBUG - NAT: Using previously obtained port of 20172.
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Changing port 32401 -> 20172
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Updating mapping in puncher thread 0x483fed0
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Creating puncher.
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Switching to NAT-PMP strategy.
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Creating NATPmPPuncher.
Mar 26, 2013 09:37:24 [0xb0aa9000] DEBUG - MyPlex: Setting manual port mode to 0.
Mar 26, 2013 09:37:24 [0xb0aa9000] DEBUG - NAT: Setting manual port mode: 0
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Initializing NAT-PMP, success=1
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Finding public address from NAT-PMP.
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Finished NAT-PMP request, result was: Not Supported by gateway
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Found public address (success=0): 0.0.0.0
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Finding public address failed the first way, switching.
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Switching to UPnP strategy.
Mar 26, 2013 09:37:24 [0xb0289000] DEBUG - NAT: Creating NATUPnPPuncher.
Mar 26, 2013 09:37:25 [0xb0207000] DEBUG - Request: PUT /:/prefs?PublishServerOnPlexOnlineKey=false [10.0.1.20:55376] (2 live)
Mar 26, 2013 09:37:25 [0xb0207000] DEBUG -  * PublishServerOnPlexOnlineKey => false
Mar 26, 2013 09:37:25 [0xb0207000] DEBUG - MyPlex: Toggling server publish state.
Mar 26, 2013 09:37:25 [0xb0207000] DEBUG - NAT: Stopping Mapping Thread
Mar 26, 2013 09:37:27 [0xb0289000] DEBUG - NAT: Initialized UPnP, result: SUCCESS
Mar 26, 2013 09:37:27 [0xb0289000] DEBUG - NAT: Requested public address via UPnP (success=1)
Mar 26, 2013 09:37:27 [0xb0289000] DEBUG - NAT: Obtained public address of 192.0.0.2 (failed: 0 myPlex: 0).
Mar 26, 2013 09:37:27 [0xb0289000] DEBUG - NAT: Checking for change in address: old was 192.0.0.2 and new is 192.0.0.2.
Mar 26, 2013 09:37:27 [0xb0289000] DEBUG - NAT: Unmapped port via UPnP.
Mar 26, 2013 09:37:27 [0xb0289000] DEBUG - NAT: Added mapping via UPnP, Public Side => 192.0.0.2:20172 (TCP), Private Side => 10.0.1.5:32400
Mar 26, 2013 09:37:27 [0xb0289000] INFO - NAT: Mapping changed 192.0.0.2:20172 -> 10.0.1.5:32400
Mar 26, 2013 09:37:27 [0xb0289000] DEBUG - It took 0.001332 sec to serialize a list with 4 elements.
Mar 26, 2013 09:37:27 [0xb0289000] DEBUG - MyPlex: Sending Server Info to myPlex (user=shapethelola, ip=, port=20172)
Mar 26, 2013 09:37:27 [0xb0289000] DEBUG - HTTP requesting to: https://my.plexapp.com/servers.xml?auth_token=suyxRJBzpt6xe2dzdw9p
Mar 26, 2013 09:37:29 [0xb0dc6000] DEBUG - Request: GET /myplex/account [10.0.1.20:55377] (3 live)
Mar 26, 2013 09:37:29 [0xb0aa9000] DEBUG - Request: GET /myplex/account [10.0.1.20:55378] (3 live)
Mar 26, 2013 09:37:30 [0xb0dc6000] DEBUG - Request: GET /myplex/account [10.0.1.20:55379] (3 live)
Mar 26, 2013 09:37:30 [0xb0aa9000] DEBUG - Request: GET /myplex/account [10.0.1.20:55380] (3 live)
Mar 26, 2013 09:37:31 [0xb0dc6000] DEBUG - Request: GET /myplex/account [10.0.1.20:55381] (3 live)
Mar 26, 2013 09:37:31 [0xb0aa9000] DEBUG - Request: GET /myplex/account [10.0.1.20:55382] (3 live)
Mar 26, 2013 09:37:32 [0xb0dc6000] DEBUG - Request: GET /myplex/account [10.0.1.20:55383] (3 live)
Mar 26, 2013 09:37:32 [0xb0aa9000] DEBUG - Request: GET /myplex/account [10.0.1.20:55384] (3 live)
Mar 26, 2013 09:37:32 [0xb0289000] DEBUG - MyPlex: Published Mapping State <--- 422
Mar 26, 2013 09:37:32 [0xb0289000] WARN - MyPlex: Invalid response when mapping state (code=422):





















  Address timeout while connecting to 80.69.99.78:20172

Mar 26, 2013 09:37:32 [0xb0289000] DEBUG - NAT: Updating mapping complete in thread 0x483fed0.
Mar 26, 2013 09:37:32 [0xb0289000] DEBUG - NAT: Deleting puncher.
Mar 26, 2013 09:37:32 [0xb0289000] DEBUG - NAT: Deleting NATUPnPPuncher.
Mar 26, 2013 09:37:32 [0xb0289000] DEBUG - NAT: Deleting NATPmPPuncher.
Mar 26, 2013 09:37:32 [0xb0207000] DEBUG - NAT: Creating puncher.
Mar 26, 2013 09:37:32 [0xb0207000] DEBUG - NAT: Switching to NAT-PMP strategy.
Mar 26, 2013 09:37:32 [0xb0207000] DEBUG - NAT: Creating NATPmPPuncher.
Mar 26, 2013 09:37:32 [0xb0207000] DEBUG - NAT: Initializing NAT-PMP, success=1
Mar 26, 2013 09:37:32 [0xb0207000] DEBUG - NAT: Finding public address from NAT-PMP.
Mar 26, 2013 09:37:32 [0xb0207000] DEBUG - NAT: Finished NAT-PMP request, result was: Not Supported by gateway
Mar 26, 2013 09:37:32 [0xb0207000] DEBUG - NAT: Found public address (success=0): 0.0.0.0
Mar 26, 2013 09:37:32 [0xb0207000] DEBUG - NAT: Finding public address failed the first way, switching.
Mar 26, 2013 09:37:32 [0xb0207000] DEBUG - NAT: Switching to UPnP strategy.
Mar 26, 2013 09:37:32 [0xb0207000] DEBUG - NAT: Creating NATUPnPPuncher.
Mar 26, 2013 09:37:33 [0xb0dc6000] DEBUG - Request: GET /myplex/account [10.0.1.20:55385] (3 live)
Mar 26, 2013 09:37:35 [0xb0207000] DEBUG - NAT: Initialized UPnP, result: SUCCESS
Mar 26, 2013 09:37:35 [0xb0207000] DEBUG - NAT: Requested public address via UPnP (success=1)
Mar 26, 2013 09:37:35 [0xb0207000] DEBUG - NAT: Unmapped port via UPnP.
Mar 26, 2013 09:37:35 [0xb0207000] DEBUG - NAT: Deleting puncher.
Mar 26, 2013 09:37:35 [0xb0207000] DEBUG - NAT: Deleting NATUPnPPuncher.
Mar 26, 2013 09:37:35 [0xb0207000] DEBUG - NAT: Deleting NATPmPPuncher.
Mar 26, 2013 09:37:35 [0xb0207000] DEBUG - NAT: Deleting NAT puncher thread 0x483fed0
Mar 26, 2013 09:37:35 [0xb0207000] DEBUG - MyPlex: Toggling server publish state.
Mar 26, 2013 09:37:41 [0xb0aa9000] DEBUG - Request: PUT /:/prefs?PublishServerOnPlexOnlineKey=true [10.0.1.20:55386] (3 live)
Mar 26, 2013 09:37:41 [0xb0aa9000] DEBUG -  * PublishServerOnPlexOnlineKey => true
Mar 26, 2013 09:37:41 [0xb0aa9000] DEBUG - MyPlex: Toggling server publish state.
Mar 26, 2013 09:37:41 [0xb0aa9000] DEBUG - NAT: Starting Mapping Thread.
Mar 26, 2013 09:37:41 [0xb0aa9000] DEBUG - NAT: Using previously obtained port of 20172.
Mar 26, 2013 09:37:41 [0xb0aa9000] DEBUG - NAT: Creating NAT puncher thread 0x34a1880
Mar 26, 2013 09:37:41 [0xb0289000] DEBUG - NAT: Updating mapping in puncher thread 0x34a1880
Mar 26, 2013 09:37:41 [0xb0289000] DEBUG - NAT: Creating puncher.
Mar 26, 2013 09:37:41 [0xb0289000] DEBUG - NAT: Switching to NAT-PMP strategy.
Mar 26, 2013 09:37:41 [0xb0289000] DEBUG - NAT: Creating NATPmPPuncher.
Mar 26, 2013 09:37:41 [0xb0aa9000] DEBUG - MyPlex: Toggling server publish state.
Mar 26, 2013 09:37:41 [0xb0289000] DEBUG - NAT: Initializing NAT-PMP, success=1
Mar 26, 2013 09:37:41 [0xb0289000] DEBUG - NAT: Finding public address from NAT-PMP.
Mar 26, 2013 09:37:41 [0xb0289000] DEBUG - NAT: Finished NAT-PMP request, result was: Not Supported by gateway
Mar 26, 2013 09:37:41 [0xb0289000] DEBUG - NAT: Found public address (success=0): 0.0.0.0
Mar 26, 2013 09:37:41 [0xb0289000] DEBUG - NAT: Finding public address failed the first way, switching.
Mar 26, 2013 09:37:41 [0xb0289000] DEBUG - NAT: Switching to UPnP strategy.
Mar 26, 2013 09:37:41 [0xb0289000] DEBUG - NAT: Creating NATUPnPPuncher.
Mar 26, 2013 09:37:41 [0xb0dc6000] DEBUG - Request: GET /myplex/account [10.0.1.20:55387] (3 live)
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Initialized UPnP, result: SUCCESS
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Requested public address via UPnP (success=1)
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Obtained public address of 192.0.0.2 (failed: 0 myPlex: 0).
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Checking for change in address: old was  and new is 192.0.0.2.
Mar 26, 2013 09:37:44 [0xb0289000] WARN - NAT: Error unmapping port via UPnP - (null)
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Unmapping ports failed the first way, switching.
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Switching to NAT-PMP strategy.
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Unmapping port via NAT-PMP
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Finished NAT-PMP request, result was: Not Supported by gateway
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Unmapped port via NAT-PMP (success=0).
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Mapping port via NAT-PMP
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Finished NAT-PMP request, result was: Not Supported by gateway
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Mapped ports (success=0) private: 0 public 0
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Mapping ports failed the first way, switching.
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Switching to UPnP strategy.
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - NAT: Added mapping via UPnP, Public Side => 192.0.0.2:20172 (TCP), Private Side => 10.0.1.5:32400
Mar 26, 2013 09:37:44 [0xb0289000] INFO - NAT: Mapping changed 192.0.0.2:20172 -> 10.0.1.5:32400
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - It took 0.001469 sec to serialize a list with 4 elements.
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - MyPlex: Sending Server Info to myPlex (user=shapethelola, ip=, port=20172)
Mar 26, 2013 09:37:44 [0xb0289000] DEBUG - HTTP requesting to: https://my.plexapp.com/servers.xml?auth_token=suyxRJBzpt6xe2dzdw9p
Mar 26, 2013 09:37:49 [0xb0289000] DEBUG - MyPlex: Published Mapping State <--- 422
Mar 26, 2013 09:37:49 [0xb0289000] WARN - MyPlex: Invalid response when mapping state (code=422):





















  Address timeout while connecting to 80.69.99.78:20172

Mar 26, 2013 09:37:49 [0xb0289000] DEBUG - NAT: Updating mapping complete in thread 0x34a1880.
Mar 26, 2013 09:37:49 [0xb0289000] DEBUG - NAT: Deleting puncher.
Mar 26, 2013 09:37:49 [0xb0289000] DEBUG - NAT: Deleting NATUPnPPuncher.
Mar 26, 2013 09:37:49 [0xb0289000] DEBUG - NAT: Deleting NATPmPPuncher.
Mar 26, 2013 09:37:49 [0xb0289000] DEBUG - NAT: We're going to next poll in 8.1 hours.
 

#6

no idea, anybody?


#7

As it seems that IPv6 is supported in General, I am at least able to access with my Macbook from another ipv6 connection without using myplex but using the direct url with address:32400/web. Still, it seems that myplex is not yet supported with ipv6. As already said, I am using a DS-Lite technology thanks to my ISP which means I have both ipv4 and ipv6 but IPv4 is completely blocked thanks to NAT and this ridiculous DS-Lite technology. More and more germans will face this problem which means it would be great if Plex server could give an option to choose between ipv4 or ipv6 myplex connectivity.


#8

I have exactly the same problem as above, German ISP switchting to iov6 DS-Lite - no longer publishing PMS. Clicking on "IPV6 support" in Plex doesn't solve the issue.


#9

No thats right, you can just access the web interface via IPv6 thats it


#10

not even accessing the web interface works when I try to remote connect to my server. The server is simply unable to publish itself at all via the internet. So all I can do is access Plex while in my LAN. I did try clicking on IPv6 Portforwarding and typed in port 32400 and then manually specified it in PLEX, but that made no difference at all.


#11

I guess youre also using DS Lite with unitymedia. Im able to access the web interface from outside my home network with the IPv6 adress and/or dyndns with the ipv6 adress. But publishing myplex wont work at all at the current state, plex team needs to build in an option to do so with IPv6 instead of ipv4


#12

Same ISP, same problem... publishing of pms don't work. Are there any solutions in work?


#13

After some digging,

there is no solution for this yet so I started http://forums.plexapp.com/index.php/topic/71546-ipv6-support-for-myplex/ since this is needed.

Greetings

Jan


#14

Hello Jan,

I have the same problem. I try to get my old IPV4 back but thats difficult. There's a solution to tunnel your IP. 

I got the webadress http://tunnelbroker.net/ from a supportcall with unitymedia. If I have some time to config my account on this site I will post my experience.


#15

That wont help you at all, to be honest. Ive already set up a Tunnel but this wont help with myplex :)


#16

Ok for those in germany who suffer from ds-lite (well only Kabel-BW) if you ask nice they give a normal dual stack back:)

http://heise.de/-1969894


#17

Yea but doesnt help the others :p


#18

Ok for those in germany who suffer from ds-lite (well only Kabel-BW) if you ask nice they give a normal dual stack back:)

http://heise.de/-1969894

hi holzi,

just wanna be sure i get this right: if i call kabelBW and tell ihem i want my dual stack back, they do it- and after that i can access myplex via internet again?!

grüße knarzi


#19

Yes, KabelBW is still doing that. Unitymedia in NRW isnt


#20

Yes, KabelBW is still doing that. Unitymedia in NRW isnt

Perfect, so i'm gonna try later. Thank you!!