Guest getting 403 error when trying to comment after "Photon" activated

I don’t think the problem is related to Photon. The error mentions mod_hive, a software package your host uses to configure their servers.

It seems that a custom security rule was triggered when your reader tried to leave a comment. Unfortunately, I’m not really familiar with Hive so I’m not sure what rule “match 3” is referring to.

Could you contact your hosting provider and ask them to take a closer look? Do not hesitate to mention this thread when you contact them; if they have any questions about how Jetpack’s Comment form iFrame works, they can post here, or send us an email.

Thanks!

Hi Jeremy,

I’ve narrowed this down to specifically Jetpack Comments. After turning the Jetpack Comments off, both people who previously had problems could leave a comment. Once I turned it back on, the problem reappeared. It seems to be affecting only frequent commenters using WordPress logins.

The thing is, it’s worked flawlessly before. I have had Jetpack Comments on since the day they were available, and I’ve had the same hosting provider and plan for at least two years.

Could this be related to the latest Jetpack update?

Thanks,
Daniel

PS: The Jetpack Comments are currently off on my blog.

Could this be related to the latest Jetpack update?

I’m afraid not. The comment form lives in an iFrame, and we haven’t made any changes to that code in a while.

As I mentioned earlier, the problem is caused by a custom security rule triggered when your readers try to leave a comment. That rule is handled by your server.

Could you contact your hosting provider and ask them to take a look at this thread? They can post here if they have more questions!