Michael Boldin

Finally have an update for you – I was able to have a successful IPN delivery of a transaction today after doing the following – so it’s hard to know what the actual cause was, but can test further if you have suggestions:

1. updated plugins and themes

2. added the IP addresses from Paypal to an alllow list at my host

3. did the same with IPs to a firewall rule to allow them at Cloudflare as well

4. disabled wordfence

5. put CF into development mode.

6. resent one IPN from paypal from a previously-successful transaction. And within about 10 minutes, the IPN went through and the subscription and order were updated on my site’s woocommerce dash.

The next subscription transaction from paypal won’t happen till overnight on Tue PM…

thanks for suggesting that. I did deactivate on the network level and just got another 403 error when testing it out. That rules out wordfence at this point then?

On top of it, thank you! What you see in the screen shot is the set of IPs that paypal gave me – and I added that to my settings. But unfortunately, after another test, I’m still getting a failure. 403. If you have any other suggestions, or need any other info from me to help, please advise!

Thank you for that explanation! Paypal tech support told me that “PayPal makes use of 443 port” and that I should whitelist IPs from my firewall. On this screenshot, you can see how I added the IPs, does it look correct to you?

https://drive.google.com/file/d/1i2Oam60cZ91KCjGW16PaL3FgGI7n4WFa/view?usp=sharing

I don’t know if there’s anything I can set for the 443 port, but if you have advice, I’m all in.

really appreciate the quick responses and all the help.

Thanks for the insight on this, Adam – much appreciated!

For this particular test, is there any advantage to switching to learning mode instead of just turning the firewall off?

Does either way give me a better chance at accurately finding the cause of the problem?

Also – another issue that I noticed here is that the email being sent is actually the generic email and the template that I edited isn’t sending. so maybe that can help figure out the cause of the problem?

Membership expired template – checkbox to disable is checked.

It does have a customized template.

The email being sent is below – so whatever is causing that send doesn’t seem to be the emails extension. it’s something else.

****email sent yesterday***

Your membership at TAC Members has ended.

Thank you for your support.

View our current membership offerings here:

Log in to manage your account here:

Hi Andrew,

Turning off all PMPRO extensions is not an option, as it would kill the functionality of my site while I wait to see what happens next. Not possible with hundreds of active monthly memberships.

Can you confirm whether or not the custom code I pasted above is the same as what you’d recommend?

just posting a follow up in case this got lost in the shuffle. Appreciate any insight you can offer here!

Can confirm that adding the code snippet I used above to the top level domain did not work. Same with unchecking the option to disable and checking it again in the hopes of resetting.

The site is the same as it has been all along. no code changes, no changes at all recently. it’s possible this has been going on longer than I’m aware of, and I’d think that’s pretty probable.

My biggest questions to start are still – is the code snippet i’m using deprecated or is this the correct code – since I can’t see it on your site?

And – should the code be installed on the subdomain where PMPro is managing memberships or should it be on the top level domain to function properly?

My site is setup as follows:

shop subdomain – woocommerce site, with PMPro woocommerce add on to associate WC orders with PMPro membership.s

members subdomain – controlled by the PMPro network subsite helper addon

my top level domain – only network subsite helper is active here.

can confirm that another email was sent today to a test account that I had set to have the membership expire this morning. I’m running PMPro and extensions on a subdomain of my site and that’s where the code snippet has been added for all these years.

As a test, i’ve got that same membership set to expire on 02-27 – and have added the code snippet to the top level domain to see if that does the trick. does this sound like something that could be the issue to you?

Thanks for the reply, Andrew. I was told to use the code snippet because the templates admin editor wasn’t working for some reason. And it worked for years. …but recently seems to be having some troubles.

No longer a plus members, so unable to see if the Code Recipe to Automatically Disable All Email is different than what I’ve been using. If it is, I’d like to try it. Otherwise, open to suggestions of how to resolve

on it, thanks Shawn!

works great, thank you for your help!

Awesome, thank you for updating me on this! Can you recommend some custom CSS that I can use to remove the top pagination only – but keep the bottom?