New paid subscriptions today are being registered properly by Stripe, but the membership status is not being updated in Ghost. The Stripe ID is appearing in the Ghost member list CSV files, so some contact is working.
Stripe reports a Pending Webhook Response. I’ve tried giving the system a nudge by following the advice to a similar comment here, but that does not appear to help, assuming I followed the advice correctly.
A search for Stripe and Crowdstrike yields nothing useful. Perhaps it’s nothing to do with that? I’m hosted in MagicPages and have emailed @jannis
Are others having the same problem? I’m currently writing apology emails to paying members who cannot sign in and handing out complimentary memberships.
Just wanted to quickly jump in here to share some further insights @fatshark and I had with this.
Interestingly, none of the webhooks from Stripe actually reached the Magic Pages “world”, but were shown as rejected in Stripe. After a manual resend, they did, however, end up in @fatshark’s Ghost site. Over time, the data was also synchronised.
We’re keeping an eye on it to see if we can spot any pattern, but as of now, my best guess is that there was a hiccup somewhere in the connection between Stripe and the Magic Pages severs, given that Stripe reports the webhooks as send, but Magic Pages never received them.
All very perplexing … but everything worked out in the end … with thanks to @jannis for the half dozen emails we exchanged very late last night, and for going the extra mile and subscribing to my site for testing purposes.
A couple of extra points. All the subscriptions happened in a 4 hour window late afternoon/early evening. Having manually resent the webhooks - originally rejected with a 401 authorisation error - around midnight it took 7-12 hours for the subscribers to appear on my site with the status (“paid”) correct. For two of the subscribers, this occurred when they logged into the site today. The Congratulations! email and status update is within a minute or so of them signing in.
Yet again, great support from @jannis at MagicPages even if neither of us understand quite what caused the problem .
… with thanks to 
.