I discovered the culprit, actually it is related to the traffic, but not because the server is stressed. There was a bug in the cache layer: if a page was loaded in a browser before a share (so very often since the hight traffic), it missed the custom twitter/opengraph meta that are conditionally generated. Now it has been fixed, let me know if you experience any other glitch.

Reply to this note

Please Login to reply.

Discussion

No replies yet.