# Insecure fonts requests

**URL:** <https://meta.discourse.org/t/insecure-fonts-requests/261118>\
**Category:** Support\
**Created:** [April 9, 2023, 7:31pm UTC](https://meta.discourse.org/t/insecure-fonts-requests/261118 "2023-04-09T19:31:44Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![silverdr](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@silverdr](https://meta.discourse.org/u/silverdr)\
**Post date:** [April 28, 2023, 11:04pm UTC](https://meta.discourse.org/t/insecure-fonts-requests/261118/10 "2023-04-28T23:04:01Z")

</div>

As mentioned in the original post, in my case certificate and everything is correct and valid but all connections to the outside are handled by a reverse-proxy (nginx, obviously ;-), while connection to discourse goes over unix socket. Meaning I have  
`templates/web.socketed.template.yml`  
rather than any of those you mention. Still - this should not need to cause static URLs have hardcoded explicit `http:` schema

---

_[View the full topic](https://meta.discourse.org/t/insecure-fonts-requests/261118)._