cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Webhook with accept host can not ping or trigger on secure server

I've intergrated the webhook in our Dev server with http (not secure) and it's working fine, then deploy to the production server using https (secured) and our authorize account is in LIVE mode. When i tried to use "Test Webhook" (ping) in the portal, it said "Error: The ping operation failed. This could be due to connectivity issues, invalid url or server downtime. Check the url details for the webhook and try again.".  

 

Two server are excactly the same environment, but we can not ping to our production from webhook which configured on the Authorize Portal. It's also can not trigger and receive any notification on our server. 

 

I only see the different between Dev and Production server is the secure or not.

 

Do you have any solution for this? Thanks in advance.

htkt89
Member
1 ACCEPTED SOLUTION

Accepted Solutions
3 REPLIES 3

Hello @htkt89 

 

Are you using standard port 443 for your secure connection? You might also confirm that your endpoint supports a TLS 1.2 connection.

 

Richard

RichardH
Administrator Administrator
Administrator

Hi @RichardH :

 

Are you using standard port 443 for your secure connection?

-> Yes, we are using port 443 for secure connection.

 

You might also confirm that your endpoint supports a TLS 1.2 connection.

-> Do you mean your service only support later TLS  1.2? We're using the TLS 1.0.

 

Can you please confirm this is the cause of this issue?

Thanks for your help.

htkt89
Member

@htkt89 

 

Yes, we require a TLS 1.2 connection.

 

https://support.authorize.net/s/article/Authorize-Net-Support-for-SSL-TLS-FAQ

 

Richard