Service monitor node-exporter endpoint in a down state. Error: context deadline exceeded

[amwinshusker]

I've deployed the prometheus operator v.9.0. All of the service monitors are in an up state except node-exporter. When I port forward node-exporter service, I am not able to access via https but I can with http (error in Chrome is ERR_SSL_PROTOCOL_ERROR). Accessing with http shows all of the metrics. The node-exporter pods shows a volume mount for kube-api-access that appears to be valid. There is a secret labeled node-exporter-token that appears to be valid. The logs on node-exporter container shows msg="TLS is disabled." http2=false, but I read in a different post that TLS is terminated with the sidecar kube-rbac-proxy. Here are the logs for kube-rbac-proxy:
I0602 14:45:57.621699 2487718 main.go:180] Valid token audiences:
I0602 14:45:57.819305 2487718 main.go:284] Generating self signed cert as no cert is provided
I0602 14:46:26.820582 2487718 main.go:334] Starting TCP socket on [10.244.0.99]:9100
I0602 14:46:26.821689 2487718 main.go:341] Listening securely on [10.244.0.99]:9100

I previously changed the insecureSkipTLSVerify: true to false setting in prometheus-adapter-apiService.yaml due to a deployment error. Could that be my problem? I changed it because of the following error I was receiving:

APIService/v1beta1.metrics.k8s.io dry-run failed, reason: Invalid, error: APIService.apiregistration.k8s.io "v1beta1.metrics.k8s.io" is invalid: spec.insecureSkipTLSVerify: Invalid value: true: may not be true if caBundle is present