#normanlove-php
safe plume
hidden isle
safe plume
what version of our library are you using?
safe plume
we began supporting PHP 8.1 in this version from last month : https://github.com/stripe/stripe-php/blob/master/CHANGELOG.md#71050---2021-12-06 , and it looks to me like the warnings there directly relate to what we changed in that pull request(https://github.com/stripe/stripe-php/pull/1213/files) to make it compatible
so you almost certainly want to update to the latest version to fix this.
safe plume
V. 7.77.0
yeah you want to be on at least 7.105.0 if you're using PHP 8, as described above
hidden isle
Ok will do it now. much thanks
hidden isle
after updating library, im see these 2 lines in error logs, is this from the stripe library?
[Thu Jan 20 05:53:16.677806 2022] [fcgid:warn] [pid 120089:tid 121565935232768] [client 54.187.205.235:23969] mod_fcgid: stderr: stripe exception area
[Thu Jan 20 05:53:31.346942 2022] [fcgid:warn] [pid 120024:tid 121565693757184] [client 54.187.216.72:37886] mod_fcgid: stderr: stripe exception area
safe plume
not sure, that's not something I've sever seen before
maybe it's coming from your own code? Try searching your code base for the string "exception area".
hidden isle
definately not my code. I wrote every character of it, except the libraries. Im thinking its the hosting server, Dreamhost shared hosting. They have this thing called Mod security and its vicious. 🙂 and the first part of the error is mod_ , so im guessing the mod security is zapping all webhook connections. I already knew about their mod security from earlier run in and they said I had to disable it and I did. but looks like its still doing something. I have a ticket open withthem about it so we shall see. just wanted to run it by you to see if you recognize it. thanks anyway.
after searching the internet, it seems that this is a stripe library error code
searching for mod_fcgid: stderr: stripe exception area shows a few people working on stripe payments and getting that initial mod_fcgid prefix.
left sorrel
Hey @hidden isle
apologies for the delay in response.
As karllekko mentioned before, we haven't seen something like this on our end.
I'd recommend creating a ticket with Stripe Support the code snippet, errors, environment info etc so that we can hopefully reproduce it on our end.
https://support.stripe.com/contact/email