# Nicht gültiges SSL-Zertifikat WP Discourse

**URL:** <https://meta.discourse.org/t/not-valid-ssl-certificate-wp-discourse/76486>\
**Category:** WordPress\
**Created:** [20. Dezember 2017 um 14:57 UTC](https://meta.discourse.org/t/not-valid-ssl-certificate-wp-discourse/76486 "2017-12-20T14:57:47Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\
**Post date:** [20. Dezember 2017 um 19:45 UTC](https://meta.discourse.org/t/not-valid-ssl-certificate-wp-discourse/76486/9 "2017-12-20T19:45:49Z")

</div>

The `src` attribute for the avatars is set by the data that’s returned by Discourse. If you have setup a webhook for syncing comments between Discourse and WordPress, you will be getting comment data that has been cached on WordPress until a new comment is added to a topic. Hopefully that’s the problem. Let us know if this doesn’t get resolved.

---

_[View the full topic](https://meta.discourse.org/t/not-valid-ssl-certificate-wp-discourse/76486)._