Hi All:

I have a new personal site I’m putting up. It’s self-hosted on a Digital Ocean Droplet, running Plesk Obsidian and WP 6. I don’t know if links are allowed here, but the page I’m trying to root cause an issue with is this one

I tried creating a FB post that just links to this page. The link works fine, but FB debugger doesn’t show the image. After tinkering with FB debugger, I think there’s something fundamentally wrong with my apache environment. I think.

I’m using YOAST to set the OG:IMAGE tag. If you look at the page source, you can see it’s set right, and the image url is accessible…at least to direct browser users via FF/Chrome/et al.

However, the FB post doesn’t show the image. I’ve used FB Debugger to scrape, but the image never ever shows up, though the debugger gives no errors.

In my apache log, I’m getting an error CODE 206 for that page, referring to the GET request HTTP/1.0 and source Apache SSL/TLS.

Hotlink protection is NOT enabled on my site. I’ve turned off all WP security plugins (Sucuri, Wordfence) and caching plugin (Autopimize).

Anyways, the Apache Log shows error 206. I cannot figure out if this is an .HTACCESS issue, a directory security issue, an apache configuration issue.

As chief, cook, and bottle washer, I’ve only got myself to try to figure this out. I’m my own hosting service…LOL! My droplet has been working great as I’ve prototyped this site. Maybe one day I’ll move it elsewhere. But for now, this is just a hobby site I’m putting up.

So here’s my question for any apache/plesk/wordpress gurus:

How does one troubleshoot an HTTP CODE 206 error? The Apache log provides no details. Just CODE 206 from the GET request for this page. Not exactly helpful.

I’m stuck. I’m certain the problem isn’t FB, and I’m pretty sure the issue isn’t Wordpress directly. It’s probably some security issue on the hosting configuration side. The Image URL is openly accessible to browsers via a GETrequest directly or by just viewing the page. No issues with WP functionality.

But when FB systems try to request, the OG data is pulled, but the IMAGE never shows up.

So I’m asking for anyone who may have an idea on how to enable a better more detailed error detail on the apache config that may help me identify / root cause this further. In fact, I’m reasonably certain it’s my apache/hosting environment. But like I said, plesk shows that HOTLINKING is NOT enabled, but the log does show code 206.

Any advice would greatly be appreciated.

3 Spice ups

@bubbaspicewny ​ Check this out. There is a facebook post debugger. It might have some idea why your posts aren’t connecting correctly. Sharing Debugger - Meta for Developers

Thank you. I’ve been using that. Scraping using the FB debugger never shows the image from the page. The OG:IMAGE info displayed in the debugger is correct. But the image never displays using the scrape of that tool or in the FB post itself that I’ve made.

There is a corresponding log event in my Apache Logs when trying to scrape using the FB debugger.

I have used https://opengraph.xyz to test and it all shows fine from that site.

I don’t know for sure that CODE 206 is indicating a HOSTING PROBLEM as it is saying that the page is partially rendering at the request using the FB Debugger. But the image never shows in FB or in FB debugger. It could be an FB problem. It’s just so hard to isolate.

@bubbaspicewny ​ I cant remember the last time I had to work on this but have you tried fixing this issue?

Warnings That Should Be Fixed

Missing Properties
The following required properties are missing: fb:app_id

@bubbaspicewny ​ Nope that wont fix your issue cause I just tested on our business site and it works fine. Hmm let me see if I can find any notes on this.

1 Spice up

@bubbaspicewny ​ Are you caching your site with a plugin?

Looking up specifically the HTTP Status Code 206 means that the server is delivering only part of the resource requested by the client due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams. This is normal for Facebook scraper cause it doesn’t need all the data from the page and its doing this to save on data consumption.

Check your execution time / timeout settings and see if increasing those times fixes this issue.

1 Spice up

I am using Autoptimize in WP, but have it disabled.

i will check execution time / timeout settings. Really appreciate your help.