# PushPublishRTMP doesn't work with IPv6 **URL:** \ **Category:** Wowza Streaming Engine\ **Created:** [August 1, 2014, 7:42am UTC](https://community.wowza.com/t/pushpublishrtmp-doesnt-work-with-ipv6/34025 "2014-08-01T07:42:24Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Dyonisius\_Visser](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@Dyonisius\_Visser](https://community.wowza.com/u/Dyonisius_Visser)\ **Post date:** [August 1, 2014, 7:42am UTC](https://community.wowza.com/t/pushpublishrtmp-doesnt-work-with-ipv6/34025/1 "2014-08-01T07:42:24Z")
Hi I’ve managed to set up WSE4.0.5 so that it picks up a stream from our Axis Q1755 camera, and then sends it to Youtube Live. This is done using the instructions on **[https://www.wowza.com/docs/how-to-stream-to-youtube](https://www.wowza.com/docs/how-to-stream-to-youtube)**. This works great when the box has dual stack addresses (IPv4 + IPv6). The production box is meant to be IPv6 only, which seems to ALMOST succeed. Various bits can do IPv6, for instance by using the **-Djava.net.preferIPv4Stack=false** statement. Unfortunately there is one thing that is failing. First, what does work: - VM is IPv6-only (Ubuntu 14.04) - **/usr/bin/WowzaStreamingEngined** is running fine on IPv6 - **/usr/bin/WowzaStreamingEngineManagerd** is running fine on IPv6 - By using an HTTP proxy the license manager is also kept happy (it requests URLs with literal IPv4 addresses, but that’s another issue) - The Axis camera stream is being picked up OK (i.e. I can watch it fine using the “Test Players”) ---
**Author:** ![Dyonisius\_Visser](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@Dyonisius\_Visser](https://community.wowza.com/u/Dyonisius_Visser)\ **Post date:** [August 1, 2014, 8:07am UTC](https://community.wowza.com/t/pushpublishrtmp-doesnt-work-with-ipv6/34025/2 "2014-08-01T08:07:25Z")
Update 🙂 I’ve seen some bugs in the past with IPv6 only applications where the IPv4 address was used, despite that fact that the host name resolved to both IPv4 and IPv6. This obviously is an issue when there is no IPv4 connectivity. The hostnames [a.rtmp.youtube.com](http://a.rtmp.youtube.com) and [b.rtmp.youtube.com](http://b.rtmp.youtube.com) both have A and AAAA records: ```auto visser@cajones:~$ host a.rtmp.youtube.com a.rtmp.youtube.com is an alias for rtmp.l.google.com. rtmp.l.google.com has address 74.125.136.150 rtmp.l.google.com has IPv6 address 2a00:1450:4013:c01::96 visser@cajones:~$ host b.rtmp.youtube.com b.rtmp.youtube.com is an alias for nonxt1.l.google.com. nonxt1.l.google.com has address 173.194.137.230 nonxt1.l.google.com has address 173.194.137.231 nonxt1.l.google.com has address 173.194.137.232 nonxt1.l.google.com has address 173.194.137.233 nonxt1.l.google.com has address 173.194.137.234 nonxt1.l.google.com has address 173.194.137.235 nonxt1.l.google.com has address 173.194.137.236 nonxt1.l.google.com has address 173.194.137.237 nonxt1.l.google.com has address 173.194.137.238 nonxt1.l.google.com has address 173.194.137.239 nonxt1.l.google.com has address 173.194.137.240 nonxt1.l.google.com has address 173.194.137.241 nonxt1.l.google.com has address 173.194.137.242 nonxt1.l.google.com has address 173.194.137.243 nonxt1.l.google.com has address 173.194.137.244 nonxt1.l.google.com has address 173.194.137.245 nonxt1.l.google.com has address 173.194.137.246 nonxt1.l.google.com has address 173.194.137.247 nonxt1.l.google.com has address 173.194.137.248 nonxt1.l.google.com has address 173.194.137.249 nonxt1.l.google.com has IPv6 address 2a00:1450:4009:34::10 ``` I just manually created two DNS RRs in my own zone which **only** list AAAA records: ```auto visser@cajones:~$ host rtmp-a.terena.org rtmp-a.terena.org has IPv6 address 2a00:1450:4013:c01::96 visser@cajones:~$ host rtmp-b.terena.org rtmp-b.terena.org has IPv6 address 2a00:1450:4009:4a::7 ``` If I use these hostnames in **conf/PushPublishMap.txt** then the live stream is successfully delivered to Youtube 🙂 [http://www.youtube.com/watch?v=Sm8m4WeeJHg](http://www.youtube.com/watch?v=Sm8m4WeeJHg) Could it be that the Push Publishing code isn’t picking up the -Djava.net.preferIPv4Stack=false stuff? In any case, it should be considered a bug. Anyway, my system is running now without IPv4 addresses. ---
**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\ **Post date:** [August 5, 2014, 5:46pm UTC](https://community.wowza.com/t/pushpublishrtmp-doesnt-work-with-ipv6/34025/3 "2014-08-05T17:46:18Z")
> Could it be that the Push Publishing code isn’t picking up the -Djava.net.preferIPv4Stack=false stuff? Hi, I tested this and did not find any issue with Wowza Push Publish and IPv6. My test was local: rtmp pushed app to app on same instance. I set IPv6 to false in Wowza, and I disabled IPv6 in Windows 7. I used IPv6 address in Push Publish configuration, and played back from the destination app over IPv6. This may have been a network, connectivity issue of some kind between you and the youtube destination. Richard ---
**Author:** ![Dyonisius\_Visser](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@Dyonisius\_Visser](https://community.wowza.com/u/Dyonisius_Visser)\ **Post date:** [August 7, 2014, 2:02am UTC](https://community.wowza.com/t/pushpublishrtmp-doesnt-work-with-ipv6/34025/4 "2014-08-07T02:02:54Z")
Problem solved. I needed to add preferIPv6Addresses to Tune.xml as well: ```auto -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true ``` After this the stream was successfully being delivered to Youtube’s rtmp hosts: ```auto visser@coppi:~$ netstat -W | grep 1935 tcp6 0 0 coppi.terena.org:40615 2a00:1450:4007:8::10:1935 ESTABLISHED tcp6 0 0 coppi.terena.org:38680 2a00:1450:4013:c01::96:1935 ESTABLISHED ``` My Wowza machine is humming along nicely without IPv4 connectivity. Thanks to Matthew Young for helping me out here 🙂 ---
**Author:** ![Daren\_Johnson](https://avatars.discourse-cdn.com/v4/letter/d/ee59a6/32.png) [@Daren\_Johnson](https://community.wowza.com/u/Daren_Johnson)\ **Post date:** [August 1, 2014, 7:28pm UTC](https://community.wowza.com/t/pushpublishrtmp-doesnt-work-with-ipv6/34025/5 "2014-08-01T19:28:57Z")
Hi, Thanks for reporting this. Certainly seems like an issue, and we should be able to fix this in a near future release. Best regards, Daren ---
**Author:** ![Matt\_Young](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/matt_young/32/389_2.png) [@Matt\_Young](https://community.wowza.com/u/Matt_Young)\ **Post date:** [August 8, 2014, 2:43am UTC](https://community.wowza.com/t/pushpublishrtmp-doesnt-work-with-ipv6/34025/6 "2014-08-08T02:43:59Z")
Thank you for updating this thread! Glad it worked out. Thanks, Matt