#ljr95-magento-500

1 messages ยท Page 1 of 1 (latest)

queen herald
#

can you share more details about this 500 error? what is responding with that?

fluid zealot
#

Hello thank you for your help

#

I don't have one ๐Ÿ˜ฆ

#

Apart from "Premature end of script headers: index.php" in apache log

#

I increased "max_execution_time" to 3600, but it didn't change anything

#

Do you have an idea ?

queen herald
#

is this a new error for something that was working, or a new integration?

#

you'll need to provide more details about what exactly is running or happening here for me to be able to help

#

Are you sure your server is able to reach stripes api servers?
https://stripe.com/docs/ips#ip-addresses
We have a reachability tool you can try running here: https://github.com/stripe/stripe-reachability

GitHub

A bash script to test access to the Stripe API - GitHub - stripe/stripe-reachability: A bash script to test access to the Stripe API

fluid zealot
#

This is a new installation.
In fact we had installed your module 7/8 months ago and we had uninstalled it (following the doc). At that time we didn't have a similar problem.

Checking os...
OK: os check
========================================
Checking ip...
+ curl -4 --write-out \n ifconfig.co/json
{
  "ip": "91.212.26.22",
  "ip_decimal": 1540626966,
  "country": "France",
  "country_iso": "FR",
  "country_eu": true,
  "latitude": 48.8582,
  "longitude": 2.3387,
  "time_zone": "Europe/Paris",
  "asn": "AS47891",
  "asn_org": "Groupe Cyres SAS",
  "hostname": "ds530.haisoft.net",
  "user_agent": {
    "product": "curl",
    "version": "7.29.0",
    "raw_value": "curl/7.29.0"
  }
}
OK: ip check
#
========================================
Checking route...
/usr/sbin/mtr
+ mtr -n --report api.stripe.com
Start: Tue Sep 14 16:59:30 2021
HOST: ds530.haisoft.net           Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 91.212.26.254              0.0%    10    0.4   0.3   0.3   0.4   0.0
  2.|-- 91.206.156.65              0.0%    10    0.4   0.4   0.3   0.6   0.0
  3.|-- 185.90.99.4                0.0%    10    0.5   0.5   0.4   0.6   0.0
  4.|-- 193.151.86.224             0.0%    10    5.5   5.5   5.3   5.8   0.0
  5.|-- 85.31.194.54               0.0%    10   12.4  12.3  12.1  12.4   0.0
  6.|-- 78.153.231.210             0.0%    10   12.3  12.3  12.2  12.4   0.0
  7.|-- 195.66.225.175             0.0%    10   11.7  11.9  11.7  12.9   0.3
  8.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  9.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
 10.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
 12.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
 13.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
 14.|-- 150.222.241.246            0.0%    10   23.8  24.3  23.7  25.7   0.0
 15.|-- ???                        0.0%     0    0.0   0.0   0.0   0.0   0.0
OK: route check
#
========================================
Checking curl_https...
+ curl -Iv https://api.stripe.com/healthcheck
* About to connect() to api.stripe.com port 443 (#0)
*   Trying 34.241.54.72...
* Connected to api.stripe.com (34.241.54.72) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
*       subject: CN=api.stripe.com,O="Stripe, Inc",L=San Francisco,ST=California,C=US,serialNumber=4675506,incorporationState=Delaware,incorporationCountry=US,businessCategory=Private Organization
*       start date: Jan 15 00:00:00 2021 GMT
*       expire date: Sep 29 23:59:59 2021 GMT
*       common name: api.stripe.com
*       issuer: CN=DigiCert SHA2 Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
> HEAD /healthcheck HTTP/1.1
> User-Agent: curl/7.29.0
> Host: api.stripe.com
> Accept: */*
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Server: nginx
Server: nginx
< Date: Tue, 14 Sep 2021 14:59:45 GMT
Date: Tue, 14 Sep 2021 14:59:45 GMT
< Content-Type: text/plain; charset=utf-8
Content-Type: text/plain; charset=utf-8
< Content-Length: 66
Content-Length: 66
< Connection: keep-alive
Connection: keep-alive
< access-control-allow-origin: *
access-control-allow-origin: *
< Strict-Transport-Security: max-age=31556926; includeSubDomains; preload
Strict-Transport-Security: max-age=31556926; includeSubDomains; preload

<
* Connection #0 to host api.stripe.com left intact
OK: curl_https check
queen herald
#

are you sure the error is between your server and stripe, rather than your application and your magento server?

#

eg, where are you seeing the error?

fluid zealot
#

I don't know where exactly this problem comes from but 99% sure that this problem is caused by your application when as soon as I deactivate it and clear the cache I have more than 500 backoffice side error.

#

Additional information, the server is using plesk

queen herald
#

can you share your stripe account id so i can check if there are any erroring requests on our side?

#

i can appreciate that the error involves the application, but the question is whether its happening client <> magento vs magento <> stripe api

#

deleted your message because its public, and included private info

#

can you share the stripe account id like acct_1234?

fluid zealot
#

Prod : acct_1EDC8nET51jxNkbN
Preprod : acct_1JXhNJAvsuCBR8HR

#

ok thx

queen herald
#

which one are you using for this?

fluid zealot
#

Prod : acct_1EDC8nET51jxNkbN

#

The preprod uses a subdomain, could this create a conflict?

queen herald
#

your server is successfully talking to stripe

#

and i see no errored requests in our logs

#

so unless you can point to a specific failing API request from your logs, this would suggest the application is failing internally and returning a 500 error to your client

fluid zealot
#

The problem is that we cannot access the backoffice page only

#

The module is currently disabled.
Would you like me to reactivate it for the test?

queen herald
#

i honestly dont know what any of that means

#

what is a back office page here?

fluid zealot
#

backoffice magento

queen herald
#

whats the context for the timeout errors, eg when/where do you see them. Is this a browser error? server logs?

fluid zealot
#

browser error 500
server logs apache : "Premature end of script headers: index.php"

#

i increased "max_execution_time" to 3600 ...

queen herald
#

ok, so from there you will need to access the server logs to understand what's going on internally

fluid zealot
#

The only error comes from apache which says: "Premature end of script headers: index.php"

queen herald
#

hmm could be permissions on the files, or a mismatched php version, similar to this:
https://community.magento.com/t5/Installing-Magento-2-x/ERROR-500-Premature-end-of-script-headers-index-php-no-admin/td-p/54912

fluid zealot
#

I have just reactivated the module and emptied the magento cache, the backoffice is again inaccessible with a 500 error

#

The file permissions are correct I have already checked

#

I will check for mismatched php version

#

I have already seen this post, but do you have a list of php version compatible with your module?

#

Would you like the url to phpinfo?

queen herald
#

No, can you please write in to support with as much detail about the error message and version of everything as possible? if you mention my name i can find your ticket and make sure it gets routed to our magento support team

#
fluid zealot
#

avez-vous une adresse mail ร  me communiquer car en passant par le lien c'est l'a

#

do you have an email address to communicate to me because through the link it is the email address of my client

queen herald
fluid zealot
#

I just sent the email, can you please check if it is complete?

frozen furnace
#

Yup, I can see the ticket on our end!

#

We'll follow up there ๐Ÿ™‚

fluid zealot
#

Ok thank you for your help.
You must answer me directly at the address: louis.joseph.rea@gmail.com
Otherwise the follow-up will be complicated on our side ๐Ÿ™‚

frozen furnace
#

๐Ÿ‘ sounds good!