WordPress.org
Get WordPress

Make WordPress Core

Opened 4 months ago

Last modified 3 months ago

#63949 new defect (bug)

wp-cron.php should use SNI

Reported by: dmole's profile dmole Owned by:
Milestone: Awaiting Review Priority: normal
Severity: major Version: 6.8.2
Component: General Keywords:
Focuses: Cc:

Description 

> grep "SNI was provided" /var/log/apache2/error.log | tail -n 1
[Tue Sep 09 12:42:40.051340 2025] [ssl:error] [pid 605:tid 687] [client REDACTED_LOCAL_IP:44088] AH02032: Hostname REDACTED_DOMAIN_1 (default host as no SNI was provided) and hostname REDACTED_DOMAIN_2 provided via HTTP have no compatible SSL setup

> grep "09/Sep/2025:12:42:40" /var/log/apache2/other_vhosts_access.log
REDACTED_DOMAIN_2:443 REDACTED_LOCAL_IP - - [09/Sep/2025:12:42:40 -0400] "POST /wordpress/wp-cron.php?doing_wp_cron=1757436160.0413179397583007812500 HTTP/1.1" 421 3908 "-" "WordPress/6.8.2; https://REDACTED_DOMAIN_2"

Change History (2)

#1 @dmole
4 months ago

  • Summary changed from cron should use SNI to wp-cron.php should use SNI

Maybe use CURLOPT_RESOLVE or CURLOPT_CONNECT_TO before CURLOPT_URL in Requests/src/Transport/Curl.php

Last edited 4 months ago by dmole (previous) (diff)

#2 @mschluepmann
3 months ago

  • Severity changed from normal to major

I think the severity is at least major. We have a this problem here with about 130 WordPress-Installations at the moment.

Note: See TracTickets for help on using tickets.