# Was passiert, wenn ich Discourse dazu zwinge, HTTPS zu verwenden, ohne jede Ressource zu überprüfen?

**URL:** <https://meta.discourse.org/t/if-i-force-discourse-to-use-https-without-checking-every-resource-what-happens/80995>\
**Category:** Product Support\
**Created:** [20. Februar 2018 um 03:29 UTC](https://meta.discourse.org/t/if-i-force-discourse-to-use-https-without-checking-every-resource-what-happens/80995 "2018-02-20T03:29:46Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![dnsmichi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dnsmichi/32/379505_2.png) [@dnsmichi](https://meta.discourse.org/u/dnsmichi)\
**Post date:** [20. Februar 2018 um 10:52 UTC](https://meta.discourse.org/t/if-i-force-discourse-to-use-https-without-checking-every-resource-what-happens/80995/8 "2018-02-20T10:52:50Z")

</div>

One thing you can also do to verify SSL is fully operational - do the discobot tutorial with a new user and go until the certificate is rendered. If that SVG rendering fails, this is most likely an SSL error then, meaning to say that Ruby’s SSL verification failed.

I had that once when I didn’t have OCSP configured in Nginx.  
[https://monitoring-portal.org/t/new-platform-work-in-progress/51/20?u=dnsmichi](https://monitoring-portal.org/t/new-platform-work-in-progress/51/20?u=dnsmichi)

---

_[View the full topic](https://meta.discourse.org/t/if-i-force-discourse-to-use-https-without-checking-every-resource-what-happens/80995)._