WeChat pay successful notify_url suddenly not callback-CodePudding

Server network environment without any changes, the program did not upgrade, WeChat pay will be successful, but not the callback, notify_url IIS log, there is no request, to solve!

Callback POST request can normal visit, domain name, IP is tried

CodePudding user response:

Successful but not callback, it is not possible, caught or see your callback is HTTP, HTTPS instead try,

CodePudding user response:

reference 1/f, 9527 response:

success but not the callback, it is not possible, caught or see if your callback HTTP, HTTPS instead of a try,

Notify_url is an HTTP post request, IIS, there is no call log

CodePudding user response:

refer to the second floor jiangnan fisher's response:

Quote: reference 1/f, 9527 response:

Successful but not callback, it is not possible, caught or see your callback is HTTP, HTTPS instead of a try,

Notify_url is an HTTP post request, IIS, there is no call log

1) WeChat payments have been said to HTTP upgraded to HTTPS, but not mandatory, before so I don't know is you because HTTP callback url, WeChat payment notice is no longer support
2) specific IIS problem, there is no log, you want to confirm that the IIS is normal, for me, don't use the IIS, it is simple wireshark caught 80 TCP port
If you through the browser to access this url, IIS has returned, so is likely to be 1, WeChat officially cancelled for the HTTPS support

CodePudding user response:

reference 3/f, 9527 response:

Quote: refer to the second floor jiangnan fisher's response:

The
Quote: reference 1/f, 9527 response:

Successful but not callback, it is not possible, caught or see your callback is HTTP, HTTPS instead of a try,

Notify_url is an HTTP post request, IIS, there is no call log

1) WeChat payments have been said to HTTP upgraded to HTTPS, but not mandatory, before so I don't know is you because HTTP callback url, WeChat payment notice is no longer support
2) specific IIS problem, there is no log, you want to confirm that the IIS is normal, for me, don't use the IIS, it is simple wireshark caught 80 TCP port
If you through the browser to access this url, IIS has returned, and so is likely to be 1, WeChat officially cancelled for the HTTPS support

1, HTTP no problem, I have here not less than 10 cases of normal operation, a set of program
2, catching the tencent official wiresharp whitelist callback requests, program is. NET development, IIS as the carrier, any request will be log

The question now is tencent said the callback, and the server, there is no callback post request public network can be normal access

CodePudding user response:

To ask WeChat development BBS

CodePudding user response:

reference 6 buildings 9527 response:

to ask WeChat development BBS

Even with the WeChat WeChat customer service, to give opinions, basic didn't help to solve the problem

CodePudding user response:

refer to 7th floor jiangnan fisher's response:

Quote: refer to the sixth floor 9527 response:

To ask WeChat development BBS

Even with the WeChat WeChat customer service, to give opinions, to solve the problem of basic didn't help

Change the callback address domain, does not exclude the tencent server access to your server,

CodePudding user response:

Inside the WeChat pay background, https://pay.weixin.qq.com/index.php/extend/pay_setting
We want to set a WeChat payment authorization domain,