The issue is most likely occurring at the server or security layer rather than within Sonaar Events.
If Facebook's Sharing Debugger reports an HTTP 510 response, it means Facebook's crawler is unable to access the page content. Sonaar Events does not generate HTTP 510 responses itself.
Any bot-blocking or crawler-blocking configuration
Since some pages work while others fail, it suggests that a security rule or server configuration is affecting only specific URLs.
You can also test the failing URLs with a header checker or by reviewing the server access/error logs to identify what is returning the 510 response to Facebook's crawler.
When trying to share an event link on Facebook, we receive an "Access denied by security policy" error.
According to the Facebook Sharing Debugger, the issue appears to be caused by the server returning an HTTP 510 response for the event URL.
This affects Sonaar Events and some pages. However many other pages work as expected.
Here is two sample pages that return such an error:
https://www.jodel.space/event/jodelkurs-potsdam/
https://www.jodel.space/ueber-mich/
Do you know how to resolve this?
Hi,
The issue is most likely occurring at the server or security layer rather than within Sonaar Events.
If Facebook's Sharing Debugger reports an HTTP 510 response, it means Facebook's crawler is unable to access the page content. Sonaar Events does not generate HTTP 510 responses itself.
I would recommend checking:
Since some pages work while others fail, it suggests that a security rule or server configuration is affecting only specific URLs.
You can also test the failing URLs with a header checker or by reviewing the server access/error logs to identify what is returning the 510 response to Facebook's crawler.
Thanks,
Alex from the Sonaar.io Crew