The user Jeroen_Van_Der_Mark reports an issue with the WP Discourse plugin where profile pictures load via HTTP instead of HTTPS, causing SSL certificate errors. Both the WordPress and Discourse sites are using HTTPS, and the Discourse URL is correctly set to https://forum.fit.nl. The issue appears to be related to cached data from Discourse, which may not be updating to use HTTPS for avatar URLs. simon suggests that a webhook for syncing comments might be causing the cached data to retain HTTP links. After troubleshooting, Jeroen_Van_Der_Mark confirms the issue is resolved, thanking simon and pfaffman for their help.
Do you have the https URL set in the Discourse URL option on WordPress? It is used for converting any relative URLs that are returned from Discourse to Absolute URLs.
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.