WorldPay Callback Failures

Author	« Topic »
Phil ECT Moderator United Kingdom 7779 Posts	Posted - 08/21/2025 : 09:00:31 Not too sure if this is a WorldPay problem or a problem with the hosting? I'm guessing it's a host issue? Here's the response below, any thoughts? HTTP/1.1 421 Misdirected Request Date: Thu, 21 Aug 2025 14:41:36 GMT Server: Apache Strict-Transport-Security: max-age=63072000; includeSubDomains X-Frame-Options: SAMEORIGIN X-Content-Type-Options: nosniff Content-Length: 322 Connection: close Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>421 Misdirected Request</title> </head><body> <h1>Misdirected Request</h1> <p>The client needs a new connection for this request as the requested host name does not match the Server Name Indication (SNI) in use for this connection.</p> </body></html> *Contact Us* *Buy The PHP Capture Card Plugin* Rate Our Services/View Our Feedback Edited by - Phil on 08/21/2025 09:34:10
Vince Administrator 43086 Posts	Posted - 08/22/2025 : 02:38:30 Hi Phil I plugged this into google and it came up with... quote: This message is an HTTP 421 Misdirected Request error, indicating a server cannot fulfill the request because the requested hostname doesn't match the hostname provided in the Server Name Indication (SNI) during the TLS handshake. The error usually occurs with shared hosting, IP addresses, load balancers, or reverse proxies due to incorrect server or SSL certificate configurations. To fix this, ensure the server has the correct SSL certificate for the requested hostname, verify DNS settings, and confirm the server or proxy isn't misrouting the request Have you checked the SSL certificate on the site? Vince Click Here for Shopping Cart Software Click Here to sign up for our newsletter Click Here for the latest updater
Phil ECT Moderator United Kingdom 7779 Posts	Posted - 08/22/2025 : 02:44:50 quote: Have you checked the SSL certificate on the site? I have yes Looking through the Worldpay docs this is what the issue appears to be below, I've sent this to the hosts: SNI (Server Name Indication): This is a feature of the TLS protocol that allows a client to specify the hostname it wants to connect to during the SSL handshake. Many web servers host multiple websites on a single IP address, each with its own SSL certificate. SNI helps the server present the correct certificate to the client based on the requested hostname. Worldpay and SNI: It has been reported that Worldpay's callback system may have compatibility issues with SNI. This can cause problems for websites using SSL certificates without dedicated IP addresses. In such cases, if Worldpay attempts to connect to your callback URL via HTTPS, and your server relies on SNI to serve the correct certificate, the connection may fail because Worldpay isn't sending the expected SNI information. *Contact Us* *Buy The PHP Capture Card Plugin* Rate Our Services/View Our Feedback
Phil ECT Moderator United Kingdom 7779 Posts	Posted - 08/23/2025 : 03:40:37 This is now fixed, so for the benefit of others here's the procedure: If your callback url (Payment Response) in your WorldPay configuration is set to https:// change it to http:// Then add an exception for the callback url in your htaccess file so it isn't redirected/forced to https This avoids any issues with certain shared hosting configurations. No sensitive data is transmitted so there are no concerns there. *Contact Us* *Buy The PHP Capture Card Plugin* Rate Our Services/View Our Feedback Edited by - Phil on 08/23/2025 03:42:03
	« Topic »