#Vijay Deepak

1 messages ยท Page 1 of 1 (latest)

odd gulchBOT
heavy jay
#

Hi. Sounds like a network connectivity issue. Is this happening on your server, local machine, or both?

heady pagoda
#

it is happening on our server

#

All other connectivity to our server is working fine

heavy jay
#

So from that same server, you're successfully making other requests to Stripe?

heady pagoda
#

Not to stripe. I meant we are able to make connection to other servers.

heavy jay
heady pagoda
#

Seems like reachability is fine.

heavy jay
#

I don't see the OK: curl_https check

#

Was that just cut off?

heady pagoda
#

This was the last line it was cut off: OK: curl_https check

heavy jay
#

Odd

#

And that script was run on the server where you are having the above api error?

#

The same node/endpoint?

heady pagoda
#

Yes, nothing has changed in that server. Everything was running fine until today morning.

heavy jay
#

To see what happens

heady pagoda
#

We tried the above curl command in our server, it works fine.

heavy jay
#

Ok so connectivity isn't the issue

#

Have you retried creating a billing portal session via your

                        .setReturnUrl(url)
                        .setCustomer(stripeCustId)
                        .build();
                com.stripe.model.billingportal.Session portalSession = com.stripe.model.billingportal.Session.create(params);```
snippet? Has the issue resolved?
heady pagoda
#

The issue is not resolved yet. We are seeing the same error if we retries creating a billing portal session.

heavy jay
#

You don't have a load balancer or something?

#

Just 1 server/node?

heady pagoda
#

Yes

#

The customer create API works fine (Customer customer = Customer.create(param)). The snippet that i sent you earlier where we creating a billing portal session that is the one that is failing.

heavy jay
#

Super weird

#

What versinon of the sdk are you using?

#

Also can I have a request id or your account id? Just want to check some logs

heady pagoda
#

group: 'com.stripe', name: 'stripe-java', version: '20.80.0'

#

Customer ID: cus_Ku8IkHyJerUktt

heavy jay
#

Ok thanks

#

Also, do you have a test environment?

#

And is that working?

heady pagoda
#

Yes. Test mode is working fine.

#

And our test server also working fine.

heavy jay
#

This all implies a connection issue

#

Not sure why the curl command is working

#

If it's only not working on 1 server and all the versioning is the same, it's almost certainly connectivity

#

But doesn't make sense why curl works on that same IP

#

You're 100% certain you tried with curl on the same exact IP?

odd gulchBOT
heady pagoda
#

Yes, its very confusing. I just tried the curl one more time from the same server.. worked fine..

urban linden
#

Hi ๐Ÿ‘‹
I'm stepping in as @heavy jay needs to go soon

heady pagoda
#

Anything you noticed from your log?

urban linden
#

When you say "your log" what are you referring to?

heavy jay
#

I was checking their request logs to see if I picked up anything interesting

#

Required customer

#

Those are from earlier today and were issued with the Java sdk

#

Any connection errors won't make it to us though (like the one you initially shared)

heady pagoda
#

we checked logs in the stripe portal and it looks like there were errors today with the message "parameter_missing - customer".

#

Looks like started appearing around 7 a.m. PST.

#

But, from what we can see, the parameters are being sent.

urban linden
#

Do you have a request ID I can review?

heady pagoda
#

req_sdjGzcYzY6FShh

urban linden
#

This request is passing no parameters to the API. The POST body is empty

heady pagoda
#

Our logs only show connectivity issue. Maybe due to that the Post body is going empty?

urban linden
#

That is the reason our API is returning an error

heady pagoda
#

Not sure why the connectivity issue happens only for the creating billing portal session and works fine for the customer creation endpoint.

urban linden
#

Yes that is strange. Do you have a recent example of the cusomter creatioin? Is it possible that the logging of connectivity issues is actually how the API errors are being handled?

heady pagoda
#

This is an example of customer creation working fine: req_NJ1BtSs0eIQpDL. The billing poertal session immediately after that failed.

urban linden
#

This was aslo sent with no POST body

#

This worked because all fields for the Customer object are optional

heady pagoda
#

We are using the builder from the SDK. The following is the code snippet for it:

  •            SessionCreateParams params = new SessionCreateParams.Builder()
                      .setSuccessUrl(successUrl)
                      .setCancelUrl(cancelUrl)
                      .setCustomer(stripeCustId)
                      .addPaymentMethodType(SessionCreateParams.PaymentMethodType.CARD)
                      .setMode(SessionCreateParams.Mode.SUBSCRIPTION)
                      .build();*
    

Should we be not using the builder anymore and just send the parameters by using params.put ?

urban linden
#

You can use the builder syntax (unfortunately not all our docs use the Builder syntax).

heady pagoda
#

We're not sure why it's failing though.. the same code works fine on our test servers

urban linden
#

However, what I am seeing is that none of these parameters appear to pass a value to the API when you call Customer.create(params)

#

In that case I would add logging to verify that the variables being passed to the builder syntax have actual values stored in them.