# Discourse não percebe terminação SSL (conteúdo misto)

**URL:** <https://meta.discourse.org/t/discourse-not-aware-of-ssl-termination-mixed-content/121650>\
**Category:** Self-hosting\
**Created:** [Junho 29, 2019, 1:45pm UTC](https://meta.discourse.org/t/discourse-not-aware-of-ssl-termination-mixed-content/121650 "2019-06-29T13:45:08Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![btsimonh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/btsimonh/32/152331_2.png) [@btsimonh](https://meta.discourse.org/u/btsimonh)\
**Post date:** [Agosto 8, 2019, 7:22am UTC](https://meta.discourse.org/t/discourse-not-aware-of-ssl-termination-mixed-content/121650/8 "2019-08-08T07:22:43Z")

</div>

Eu estava enfrentando o mesmo problema com o Discourse na frente do HAProxy fazendo a terminação SSL.  
Ativei a opção Forçar HTTPS, mas ainda recebia avisos de conteúdo misto (por exemplo, no favicon).  
No entanto, ao fazer o upload de um logotipo, todos os avisos desapareceram — inclusive para o favicon, que eu não alterei.  
Então, talvez ele recalcule as URLs de todas as imagens ao fazer o upload de qualquer imagem (pelo menos para as imagens do sistema base…)?

---

_[View the full topic](https://meta.discourse.org/t/discourse-not-aware-of-ssl-termination-mixed-content/121650)._