# HTTPS browser requests failing to Icecast server

**URL:** <https://community.letsencrypt.org/t/https-browser-requests-failing-to-icecast-server/234845>\
**Category:** Help\
**Created:** [March 10, 2025, 12:45am UTC](https://community.letsencrypt.org/t/https-browser-requests-failing-to-icecast-server/234845 "2025-03-10T00:45:46Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\
**Post date:** [March 10, 2025, 1:50am UTC](https://community.letsencrypt.org/t/https-browser-requests-failing-to-icecast-server/234845/3 "2025-03-10T01:50:46Z")

</div>

> [@maaaaaaaaaatt](#):
>
> I can see the certificate and the key saved to my server, but they aren't showing up on [crt.sh | stream.transmission-reception.com](https://crt.sh/?q=stream.transmission-reception.com)

crt.sh is often lagging behind, certificates logged to CT should show up there eventually but it might take a while. There are other [CT search resources](https://community.letsencrypt.org/t/certificate-transparency-search-resources/203368) one can use, but in general if you actually have a cert than it's a good bet that it actually got logged, unless you're specifically getting an error from a browser about it not accepting the CT log signatures or something.

> [@maaaaaaaaaatt](#):
>
> it doesn't look like the browser is detecting them as being secured when I visit the page.

I think you'll need to be a lot more specific about what problems you're experiencing. From here it just looks like your site isn't responding on port 443 at all, which wouldn't indicate any issue with the certificate but with your firewall, router, or server settings.

---

_[View the full topic](https://community.letsencrypt.org/t/https-browser-requests-failing-to-icecast-server/234845)._