hnhegde-cli | Stripe Developers | Page 1

brave badger Mar 4, 2022, 9:12 AM

#

Hi! That's odd. What were you trying to do when you saw that error?

#

And do you saw that error only once or is it recurring?

modern drum Mar 4, 2022, 9:13 AM

#

I see it everytime I start stripe listener:

stripe listen --forward-to localhost/api/checkout_webhook/ --latest --log-level=debug

#

attached the full log

📎 message.txt

brave badger Mar 4, 2022, 9:19 AM

#

Thanks! I tried to reproduce but it's working for me.
Note that "r.stripe.com/0" is only used for analytics purposes. Maybe you have a firewall (or something similar) blocking these requests?

modern drum Mar 4, 2022, 9:21 AM

#

hmm...ok. Thats why its printed in debug logging.

#

Thanks for looking into. I can safely ignore this message then?

brave badger Mar 4, 2022, 9:23 AM

#

If then events are still being forwarded to your URL, then yes! This just means that some analytics data won't get to Stripe.

modern drum Mar 4, 2022, 10:00 AM

#

I get this on idle and no events are received:

[Fri, 04 Mar 2022 15:28:23 IST] DEBUG websocket.Client.connect: Websocket connection error error=dial tcp: i/o timeout message=
[Fri, 04 Mar 2022 15:28:23 IST] DEBUG websocket.client.Run: Failed to connect to Stripe. Retrying...
[Fri, 04 Mar 2022 15:28:34 IST] DEBUG websocket.Client.connect: Dialing websocket url=wss://stripe-cli.stripe.com/subscribe/acct_1JVG9tF82kR6pkQ4?websocket_feature=webhook-payloads

Can you kindly advise?

#

cli used to auto-connect after idle.

brave badger Mar 4, 2022, 10:04 AM

#

That's odd, that may be linked to your previous issue. Would you mind sending your question directly to Stripe support here https://support.stripe.com/?contact=true
Make sure to include all relevant logs (as you did above).

#hnhegde-cli