# Streaming should support HTTPS

**URL:** https://discourse.indi.software/t/streaming-should-support-https/196
**Category:** Bug Report
**Tags:** Feature
**Created:** [September 5, 2024, 10:41am UTC](https://discourse.indi.software/t/streaming-should-support-https/196 "2024-09-05T10:41:57Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![juttrikes](https://discourse.indi.software/letter_avatar_proxy/v4/letter/j/ba8739/32.png) [@juttrikes](https://discourse.indi.software/u/juttrikes)
#### Post date: [September 5, 2024, 10:41am UTC](https://discourse.indi.software/t/streaming-should-support-https/196/1 "2024-09-05T10:41:57Z")

</div>

MAFA version: 1.9.9

HTTP Streaming settings should support HTTPS protocol. Currently there’s no way to set HTTPS - the URL and port expect HTTP, no substitutes.

---

<div class="post-metadata">

### Author: ![Alex\_B](https://discourse.indi.software/letter_avatar_proxy/v4/letter/a/5f8ce5/32.png) [@Alex\_B](https://discourse.indi.software/u/Alex_B)
#### Post date: [September 5, 2024, 11:06am UTC](https://discourse.indi.software/t/streaming-should-support-https/196/2 "2024-09-05T11:06:25Z")

</div>

The HTTP streaming option in MAFA is used to connect to the httpd output of MPD.

MPD provides only HTTP server for output streaming ([MPD httpd output plugin](https://mpd.readthedocs.io/en/latest/plugins.html#httpd)).

(If you want to add an external HTTPS URI to the player queue, you can do that from the “Add URL” menu item in the Player menu.)

---

<div class="post-metadata">

### Author: ![juttrikes](https://discourse.indi.software/letter_avatar_proxy/v4/letter/j/ba8739/32.png) [@juttrikes](https://discourse.indi.software/u/juttrikes)
#### Post date: [September 6, 2024, 3:16am UTC](https://discourse.indi.software/t/streaming-should-support-https/196/3 "2024-09-06T03:16:01Z")

</div>

yes, but:

- I don’t have a direct access to mpd output or network, only through a proxy server with HTTPS
- the bluetooth controls work only with the internal player and only when it’s playing the MPD output, not the playlist

---

<div class="post-metadata">

### Author: ![Alex\_B](https://discourse.indi.software/letter_avatar_proxy/v4/letter/a/5f8ce5/32.png) [@Alex\_B](https://discourse.indi.software/u/Alex_B)
#### Post date: [September 6, 2024, 11:12am UTC](https://discourse.indi.software/t/streaming-should-support-https/196/4 "2024-09-06T11:12:49Z")

</div>

> [@juttrikes](#):
>
> I don’t have a direct access to mpd output or network, only through a proxy server with HTTPS

How do you tunnel/proxy the MPD connection? Would it be possible to do the same for the HTTP stream?  
When I want external access I open two reverse tunnels with ssh from a public server to the local MPD. One for the MPD connection and the other for the HTTP stream.

> [@juttrikes](#):
>
> the bluetooth controls work only with the internal player and only when it’s playing the MPD output, not the playlist

The app can only receive Bluetooth device events when it is the current media session. So yes, only when it is playing using the internal player that it controls.

When the app is at the foreground you can skip tracks or control the volume using the device’s volume buttons (settings → Behavior → “Hardware volume buttons”).

---

<div class="post-metadata">

### Author: ![juttrikes](https://discourse.indi.software/letter_avatar_proxy/v4/letter/j/ba8739/32.png) [@juttrikes](https://discourse.indi.software/u/juttrikes)
#### Post date: [September 6, 2024, 2:29pm UTC](https://discourse.indi.software/t/streaming-should-support-https/196/5 "2024-09-06T14:29:55Z")

</div>

My ISP hooks into HTTP connection to inject their ads and garbles the audio traffic, I have to use HTTPS.

---

<div class="post-metadata">

### Author: ![Alex\_B](https://discourse.indi.software/letter_avatar_proxy/v4/letter/a/5f8ce5/32.png) [@Alex\_B](https://discourse.indi.software/u/Alex_B)
#### Post date: [September 8, 2024, 6:46am UTC](https://discourse.indi.software/t/streaming-should-support-https/196/6 "2024-09-08T06:46:35Z")

</div>

OK. I’ll look into adding HTTPS support for the streaming but can’t promise it will be soon.

Although I’d recommend setting up a VPN or another tunneling solution.  
Also, did you try a custom port for the HTTP proxy? Maybe your ISP only targets port 80.

---

<div class="post-metadata">

### Author: ![juttrikes](https://discourse.indi.software/letter_avatar_proxy/v4/letter/j/ba8739/32.png) [@juttrikes](https://discourse.indi.software/u/juttrikes)
#### Post date: [September 9, 2024, 5:03am UTC](https://discourse.indi.software/t/streaming-should-support-https/196/7 "2024-09-09T05:03:07Z")

</div>

I did try a custom port, yes
