• Resolved dankfresh

    (@dankfresh)


    There has been a recent issue with sharing posts on social media. We are using Yoast 20.8 to insert the OG tags for a post which has been working fine up until the recent Really Simple SSL update to vers 7.0+. We are currently using Really Simple SSL Version 7.0.2. The OG tags are still inserted, however, Facebook Debugger and other OG validators are returning a 4xx response code or not identifying the og:image tag. There has been some issue with using https protocol for the og:image tag in the past.

    The free version 7.0.2 is using htaccess 301 redirects with no issue. No hardening settings, no security headers.

    Disabling the RSSSL plugin (but keeping https://) restores the functionality, and the OG tags are recognized and work as expected.

    Curious if anyone else is experiencing this.

    WordPress 6.2.2
    Really Simple SSL 7.0.2
    Yoast 20.8

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    @dankfresh if you also deactivate the .htaccess redirect, 301 redirect and the mixed content fixer, do you still have the issue?

    I just checked with a site with Yoast 20.8 and Really Simple SSL on 7.0.2 installed, .htaccess redirect enabled, and tested some pages in the facebook debugger. I couldn’t reproduce any issues.

    If you look in the source code, is the og:url with https?

    Thread Starter dankfresh

    (@dankfresh)

    Hello Rogier! I appreciate the quick response.

    I have tried both implicitly setting the og:url to http and https, and even used a filter for

    wpseo_opengraph_image

    to set the og:url to use http and og:image:secure_url to use https with no real difference in results.

    I also attempted toggling the mixed content fixer and .htaccess vs. php vs. no redirect.

    Turning off the redirect and mixed content fixer entirely results in the og:image being http and the Facebook debugger/OG checker returning the correct results for all of the open graph data (image included).

    Using any sort of redirect in the settings OR turning on the mixed content fixer results in a 418 response code from Facebook debugger (which… I am baffled by), and no response of an image.

    The WordPress site’s settings has the URL using the https protocol.

    I appreciate any insight you can provide. Thank you.

    • This reply was modified 1 year, 10 months ago by dankfresh.
    Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    The 418 response is strange. When I search for this code I see some references to iThemes, for example:
    https://wordpress.stackexchange.com/questions/103089/why-better-wp-security-plugin-returns-418-im-a-teapot-error/103140#103140

    Are you using that plugin by any chance? Or another plugin that contains functionality to block requests?

    Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    Please also check if hotlink protection is enabled on the server. The 418 response also might be a hosting response. I noticed DreamHost uses it for example.

    Thread Starter dankfresh

    (@dankfresh)

    Again, the insight and troubleshooting are very appreciated.

    Hotlink protection is not enabled.

    There are no security plugins aside from Really Simple SSL. The only other plugins are Yoast and ACF.

    This is also a recent occurrence. The site has been functional and capable of sharing the correct OG tags (and it pulling the correct images) for over 2 years now. Within the past 2 weeks this has started occurring, and RSSSL and Yoast have had a few automatic updates during that time period, so that’s where I started my investigation.

    Nevertheless, I am going to mark this ticket as resolved because I am really starting to suspect that the issue lives outside of the plugin. OG tags are finicky things in my experience anyway.

    If you happen to know a more reliable OG tags debugger than Facebook (and opengraphcheck.com appears to be down), that would be helpful.

    I am grateful for your efforts to help diagnose. Thank you again.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘OG Image Social Media Sharing Issues’ is closed to new replies.