Difference between revisions of "Curl: (52) Empty reply from server"
Jump to navigation
Jump to search
(5 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
− | |||
curl: (52) Empty reply from server | curl: (52) Empty reply from server | ||
− | + | ||
Solution: try https:// | Solution: try https:// | ||
Line 12: | Line 11: | ||
establish a secure connection to it. To learn more about this situation and | establish a secure connection to it. To learn more about this situation and | ||
how to fix it, please visit the web page mentioned above. | how to fix it, please visit the web page mentioned above. | ||
+ | |||
+ | == Related == | ||
+ | * <code>[[curl --insecure]]</code> | ||
+ | * <code>[[curl -m]]</code> | ||
+ | * <code>[[kubectl logs -n nginx-ingress nginx-ingress-controller]]</code> | ||
+ | * <code>[[no endpointslices for target port]]</code> | ||
== See also == | == See also == |
Latest revision as of 08:18, 16 February 2024
curl: (52) Empty reply from server Solution: try https://
curl: (60) SSL certificate problem: self signed certificate More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above.
Related[edit]
curl --insecure
curl -m
kubectl logs -n nginx-ingress nginx-ingress-controller
no endpointslices for target port
See also[edit]
Advertising: