Problem with http to https icecast2 radio

1. Caddy version (caddy version):

Caddy v1.0.4

2. How I run Caddy:

sudo caddy run

https://0x29a.fi for the website and for the icecast2 http://0x29a.fi:8000/0x29a

a. System environment:

Ubuntu 16.04.6 LTS

d. My complete Caddyfile or JSON config:

0x29a.fi {
root /var/www/web
gzip
fastcgi / /var/run/php/php7.0-fpm.sock php  
}

3. The problem I’m having:

I have problem to serve icecast2 url to https. My normal site works fine https://0x29a.fi, but icecast2 not working with audio elements because:

With Chrome 80, released in January, Chrome attempts to [automatically upgrade HTTP media requests to HTTPS]. If the server doesn’t supply HTTPS media, the request will fail.

I need to serve http:// 0x29a .fi :8000/0x29a via https

5. What I already tried:

I’m trying to use this example: https://mediarealm.com.au/articles/icecast-https-ssl-setup-lets-encrypt/ but not good results.

http: TLS handshake error from ip-address:674: tls: first record does not look like a TLS handshake

[INFO] 81.4.103.120 - No such site at :80 (Remote: ip-address, Referer: http://ip-address:80)

letsencrypt cert creation: Problem binding to port 80: Could not bind to IPv4 or IPv6.

I’m not sure we can help you with this.

The URL you’ve given specifies the http:// scheme. You can’t serve HTTPS to a client that requests HTTP. The closest would be serving a redirect via HTTP.

Your above Caddyfile should already serve HTTPS on port 443, and should already redirect all HTTP requests.


P.S.: Caddy v1 is now obsolete and is no longer receiving updates. I’d strongly recommend considering an upgrade to Caddy v2. Upgrading to Caddy 2 — Caddy Documentation

This topic was automatically closed after 30 days. New replies are no longer allowed.