#AndySeigel

1 messages ยท Page 1 of 1 (latest)

tame pecanBOT
last sedge
#

Hello again! Are you able to trigger a webhook and then dump the network logs for your server during that time to see what's being received?

#

Also, do you have the code for your webhook handler for me to take a look at?

normal spoke
#

Also, I did a resend with one of the requests in the dashboard -> and it went through successfully. (which is even more confusing).

#

Lets see, which network logs did you mean -> IIS, event viewer, or something else

#

I will get the code for the handler now

last sedge
#

I'm not very familiar with IIS, so I'm not sure. I've only used Apache and NGINX

#

Both on Linux, so I'm used to a Bash CLI when dumping logs

normal spoke
#

I'll see what I can dig up for that

last sedge
#

Taking a look now

normal spoke
#

if you look at the dashboard you can ignore the last item sent (the 2:53pm is after the logs are captured)

peak wagon
#

Hi, stepping in for two-shows as they had to step away.

normal spoke
#

No problem, thanks for joining. Let me know if I can provide more information. I really appreciate the help.

peak wagon
#

After further reviewing, this appears to be a network issue. Could you check your server logs and see if there was any downtime/high load in that window?

normal spoke
#

It depends how far back you look in that log right, you might have some catching up to do but one of the messages above was the server was actually off. Now that its back on, the requests are still not consistently getting through. I'm not in production yet, though its hosted, so I can re-try any requests if that helps

peak wagon
#

Sounds good

normal spoke
#

So what is your advise, with what to look at next with these intermittant requests?

#

I just got another through successfully... did something just change on the stripe end?

#

If this is related to the outage, does that mean that if I reboot my server in production, I will run into this problem again ? ๐Ÿ˜จ

peak wagon
#

Sorry, I read this as you were to retry and see if you were still seeing an issue. As for next steps, you'd want to improve logging to see exactly what went wrong.

Nothing has changed on our end from looking here internally.

normal spoke
#

Ok, well its working right now. Still no idea the cause, I will get as much log information as possible before coming back to this chat if it happens again. thanks for your time today @peak wagon and @last sedge .