403 error?

Hi Ed

That’s a strange issue, let’s see if we can fix it!

Did you or can you check plugins that minimize javascript and css? Or caching plugins like W3TOTALCACHE? Can you try disabling them?

Could you e-mail me on [email protected] so I can send you the latest beta version?

This FAQ might help:
https://www.redsandmarketing.com/plugins/wp-spamshield/troubleshooting-guide/?step=09#step_09

Please let me know what you find, ready to help!

Kind regards
David

Excellent advice, @davdebcom! We would agree.

It does look like the error message comes from WP-SpamShield.

@edbras It looks like your site is using W3 Total Cache – That will definitely cause problems. In the past it was quite good but we no longer recommend it, as it’s gone downhill in the last couple years. It definitely mangles a lot of JS and CSS, and we recently marked it as not compatible with WP-SpamShield.

I can also recommend this troubleshooting step as well to maximize compatibility with caching.

Let us know if we can be of any further help to either of you.

– Scott

Scott, thank you very much for replying!

Thanks David and Scott
I just solved it by disabling the WP-TOTALCACHE and WP-SPAM plugin’s together. Disabling only one of them, wasn’t enough.
Happy to find it, but it took a long time ??

Hi Ed

Happy it no works, I’ll make sure to test WP-SPAM with Paytium, just in case.

Kind regards
David

I encountered the following issues:
1) This morning when pressing the payment button, the plugin returned an ERR_EMPTY_RESPONSE Http error. After 15 min, this was gone :(.. Any idea what this could be ? Maybe an error at mollie ?

2) When it works correctly, I see in the apache error log, the following:
—-
[:error] [pid 26331] [client 77.171.57.105:56202] No Mollie Customer created, no fields with type name & email found, referer: https://www.bydehand.com/reis-analyse-betaalmodule/
—-
How can I solve this?
Is customer “Me” or the person trying to pay? I think the paying person, but why can’t it be created, while it shows the list of banks.

– Ed

Hi Ed

1) That could be, but I think it could have been a number of connection issue’s between your website and Mollie, if it doesn’t happen again I don’t think we will find the root cause.

2) I know it’s in the error log, but it’s actually not really an issue. More a notice. Paytium tries to create a customer at Mollie if you have enough information in your forms. It’s not required. If it doesn’t create that customer, it shows that message. I’ll make sure to remove those error’s, as they are confusing, I agree.

Regards
David

Hi David,
Thanks for the quick reply.
I hope it stays working now ??
– Ed

I have tested WP-SpamField with Paytium and in my development environment, it seems to work perfectly. So you should be able to re-enable it.

• This reply was modified 7 years, 9 months ago by davdebcom.

Ha, just noticed the 403 comes when the webhook URL is called, I’ll research this and get back to you!

Ok, thanks for looking in to it.

I noticed this in the apache error log, but I didn’t really know what to do with it, as it has no further details:
[Fri May 12 16:06:02.992098 2017] [:error] [pid 29543] [client 87.233.229.27:59350] Webhook call for tr_PmAtPWxbeH

Okay, so WP-SpamShield blocks communication by Mollie to the webhook URL. To fix this, you need to whitelist the Mollie API IP’s:
https://help.mollie.com/hc/nl/articles/213470829-Welke-IP-adressen-gebruikt-Mollie-Vanaf-welke-IP-range-kan-ik-requests-verwachten-

Hi @davdebcom,

Please get in touch with us for any help with compatibility issues. We definitely don’t block Mollie’s servers or requests, and in fact we’ve added whitelisting for Mollie. So, if it’s getting blocked, it’s for a different reason.

We have a compatibility guide for other developers, so please check that out. There is a contact form at the bottom of it that you can use to contact us. We’re glad to help bridge compatibility issues with other developers. ??

– Scott

It looks like Paytium (and Mollie payments) are no longer be blocked in the latest version of WP SpamShield.

Ok, thanks, we will have a look.