Help with Meta scraping

General
24

Thanks guys for all the help. I’m sure this is what I’m doing and I’ve double checked, but I imagine the most likely explanation is that I’ve made a mistake somewhere.

Would you be able to check?

App ID is 9144D969-8CEB-81F4-FF84-987167CF6800

Container is webApp

URL is https://www.mina.tax

Thank you!

25

@Luc_Zentar, you could try changing the index.html file at this path. It worked for me:

Снимок экрана 2023-05-03 в 11.45.58
Снимок экрана 2023-05-03 в 11.45.581716×1440 161 KB

Regards,
Alexander

26

Thank you, the OG tags are now showing on the website the but the same error persists with the Facebook crawler.

These are the requirements of the crawler, does anything in there suggest an issue?

Crawler Requirements

  • Your server must use gzip and deflate encodings.
  • Any Open Graph properties need to be listed before the first 1 MB of your website or app, or it will be cutoff.
  • Ensure that the content can be crawled by the crawler within a few seconds or Facebook will be unable to display the content.
  • Your app or website should either generate and return a response with all required properties according to the bytes specified in the Range header of the crawler request or it should ignore the Range header altogether.
  • Add to your allow list either the user agent strings or the IP addresses (more secure) used by the crawler.
  • Ensure that your app or website allows the Facebook Crawler to crawl the privacy policy associated with your app or website.

The error message remains the same, related to the range request:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head>
<body><p>{"code":8053,"message":"Invalid value 'bytes=0-524287' for 'Range' header. Invalid last byte position 524287","errorData":{}}</p></body>
</html>

Thank you

28

Hello @Luc_Zentar,

I’ve created an internal ticket to investigate and fix this issue.

Regards,
Stanislaw

29

Thank you @stanislaw.grin

I know you can’t be exact, but any help with timeframes will be so helpful. Are we talking days / weeks / months?

30

Hello @Luc_Zentar

We can’t talk about a clear timeline, but the ticket has OPEN status for now. If you need to know the status of the task, you can always ask about it in this topic.

Regards,
Inna

31

Thanks Inna, my business is pretty much on hold until I can find a solution to this. Is there any update? Is there a way for me to speed this up through consultancy fees with you?

32

@Luc_Zentar ,

We have released a fix which should fix your issue. Could you please check and confirm from your side that issue was fixed?

Regards, Andriy

33

Thank you so much everyone, it’s working now. I appreciate the fast response to this critical issue for us.