Certificate verification disabled (sslverify=false) WP-CRON

[123nadav]

Is familier with the core... have recommendation?
i active an deactive any plugin and tried shutdown the server and bring back all c-panel to default... i still get this error first time i get the website (before the cache)

and i can get inside my website in safari in the first time after i refresh is not secure.

i see a lot of topics about the issue and CA certificated change everytime... if you have OCSP stapling is can be big isiue.
what you recommend? change it? some fix?

my websites:
locksmithunit.com
locksmithunit.cat
locksmithunit.es

[123nadav]

fix the issue on safari and the HTTP is was reverse proxy issue...
but i am still stuck with the error:
Certificate verification disabled (sslverify=false) WP-CRON

from corn... now i was thinking to deactivate him from the config but is be stoped and i have
a lot of cron tasks on my websites can be damaged... what to do? how i can fix it?
maybe function?

[peterwilsoncc]

@123nadav

Trac is used for the development of WordPress core, not for providing support for individual sites. Please refer to the WordPress support forums for help, ​https://wordpress.org/support/forums

As you've been referred to the support forums, I'll close this ticket for now.

[123nadav]

I think you wrong again...
You can look, This belongs to the core files of WordPress...
and is affected by something but the files is core files
from WordPress And the issue is maybe belong to 5.5.1
​https://ibb.co/S6vSKR1

Look on the screenshots is WordPress files...
generate via WordPress and changes via core updates...

is the second time you close my post with the same answer, why?

Regards,
Nadav Levi

[123nadav]

And this not only me is many and many people suffer from the same error but they
don't know you create actually a place to trace the core and his problem. these files belong to word press
and i tell you right now we have a problem, so how is not related to the issue exactly?

[johnbillion]

It's intentional that requests to the site itself don't verify the SSL certificate. See #12609 and #47957 for all the details. This is because sites behind a reverse proxy may be using a self-signed certificate, and there is no need to verify the certificate at this point because the connection is a loopback.

The warning you're seeing is a bug in the Query Monitor plugin, which is being tracked here: ​https://github.com/johnbillion/query-monitor/issues/537 .

[123nadav]

Thank you from the bottom of my heart.
I will follow the topic you send me.

Again John thank you.
appreciate that.

Regards
Nadav Levi

Replying to johnbillion:

It's intentional that requests to the site itself don't verify the SSL certificate. See #12609 and #47957 for all the details. This is because sites behind a reverse proxy may be using a self-signed certificate, and there is no need to verify the certificate at this point because the connection is a loopback.

The warning you're seeing is a bug in the Query Monitor plugin, which is being tracked here: ​https://github.com/johnbillion/query-monitor/issues/537 .