Inconsistent metadata (request timeout) with self signed cert on remote schema

[zachequi]

Version Information

Server Version: 2.11.2 (tried v2.12.0-beta as well, same result) CLI Version (for CLI related issue): N/A

Environment

OSS

What is the current behaviour?

• Have a remote schema configured in metadata using https with a self signed certificate
• Have the domain for the remote schema in the TLS allowlist in the console
• Have consistent metadata
• Reboot hasura

What is the expected behaviour?

• Hasura reboots and still has consistent metadata

Actual Behavior

• Hasura reboots with inconsistent metadata complaining the request to the remote schema timed out.

I've tried changing our backend url to use our public remote schema URL (which has a valid signed cert instead of the internal url which is self-signed) and the issue goes away, so the issue is isolated to when our remote schema uses an https url with a self-signed certificate.

Can you identify the location in the source code where the problem exists?

If the bug is confirmed, would you be willing to submit a PR?