# HLS over HTTPS problem with Android

**URL:** <https://community.wowza.com/t/hls-over-https-problem-with-android/49934>\
**Category:** Wowza Streaming Engine\
**Created:** [October 16, 2017, 3:06pm UTC](https://community.wowza.com/t/hls-over-https-problem-with-android/49934 "2017-10-16T15:06:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alia\_Papa](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@Alia\_Papa](https://community.wowza.com/u/Alia_Papa)\
**Post date:** [October 16, 2017, 3:06pm UTC](https://community.wowza.com/t/hls-over-https-problem-with-android/49934/1 "2017-10-16T15:06:03Z")

</div>

Hello,

These past few days I have searched the forum for a solution to my problem but to no avail. There are some similar issues but none of them helped me.

I am streaming via HLS over HTTPS (I have my own certificate) with Flowplayer 7.

I am trying to test the compatibility on Android devices, but the message that I get from Flowplayer is ‘Video file not found’. I have no issue with desktop browsers, so I am focusing first to cross out server side problems.

Android seems to work perfectly fine with HLS over HTTP.

I did try to have absolute paths in the chunklist and used this properties:

```auto
cupertinoHttpRedirectEnabled = true,

cupertinoPlaylistHostProtocol = https,

cupertinoChunkHostProtocol = https

```

That I found in another question thread, but that didn’t work for me. I mean that the code worked, but it didn’t resolve my issue.

Does anybody have any other ideas on this? Since HLS means #apple, can this be the problem for Android devices?

Thanks in advance

---

<div class="post-metadata">

**Author:** ![Alia\_Papa](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@Alia\_Papa](https://community.wowza.com/u/Alia_Papa)\
**Post date:** [November 7, 2017, 1:02pm UTC](https://community.wowza.com/t/hls-over-https-problem-with-android/49934/2 "2017-11-07T13:02:27Z")

</div>

Hello everyone

So after some extensive check I traced a firewall issue at port 443.

Everything seems to be working fine now.

Best regards