Ingo Oppermann

We didn't look into this, yet.

@wallopthecat I didn't try it out, but I think you could use the `stream` functionality of nginx to achieve this (http://nginx.org/en/docs/stream/ngx_stream_core_module.html). It's basically accepting TCP connection on a defined port...

The `location` block will only be respected for HTTP requests. In order to proxy the RTMP requests, you either have to find a dedicated RTMP proxy or use the nginx...

Currently this is not possible out-of-the-box. You could modify the `conf/nginx.conf` such that it asks for a password if the player.html is accessed. You could either build your own docker...

@1nerdyguy Do you have access to a log at the Teradeck in order to see why it can't establish the RTMP connection? For RTMP to work, only H.264 is supported.

@ulope Did you follow the [OBS guide](https://datarhei.github.io/restreamer/docs/guides-obs.html)? In OBS, use `rtmp:///live` as value for "Server" and `external.stream?token=...` as value for "Stream Key".

Hi @bubbapizza, did you check out the old issue https://github.com/datarhei/restreamer/issues/129 ? It requires that you re-encode the stream.

Do you see in the logs any error messages regarding Let's Encrypt? You'll find the logs in the settings with "Expert mode" enabled (see: https://docs.datarhei.com/restreamer/knowledge-base/manual/system-settings/logging).

Did you actually enable HTTPS according to our guide? https://docs.datarhei.com/restreamer/knowledge-base/user-guides/how-can-i-use-https-with-lets-encrypt

You should edit the `audio_codec_aac` and/or `audio_codec_mp3`section in the `live.json`. It might look like this for AAC encoding: ```json "audio_codec_aac": { "outputOptions": [ "-codec:a aac", "-bsf:a aac_adtstoasc", "-af volume=6dB", ]...