You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I tried to debug on the Nginx proxy on using the curl or wget command. Here is the results:
[root@ip-10-255-3-177 nginx]# wget https://localhost:443
--2023-09-26 06:38:42-- https://localhost/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:443... connected.
ERROR: cannot verify localhost's certificate, issued by ‘/C=GB/ST=Test State/L=Test Locality/O=Org Name/OU=Org Unit Name/CN=Common Name/emailAddress=test’:
Self-signed certificate encountered.
ERROR: certificate common name ‘Common Name’ doesn't match requested host name ‘localhost’.
To connect to localhost insecurely, use `--no-check-certificate'.
[root@ip-10-255-3-177 nginx]# curl https://localhost:443
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.
This has blocked my troubleshooting
Expected Behavior
Do NOT use self-signed SSL certificate
Current Behavior
use self-signed SSL certificate
Reproduction Steps
N/A
Possible Solution
No response
Additional Information/Context
No response
Solution Version
v2.0.0
AWS Region. e.g., us-east-1
No response
Other information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
When I tried to debug on the Nginx proxy on using the curl or wget command. Here is the results:
This has blocked my troubleshooting
Expected Behavior
Do NOT use self-signed SSL certificate
Current Behavior
use self-signed SSL certificate
Reproduction Steps
N/A
Possible Solution
No response
Additional Information/Context
No response
Solution Version
v2.0.0
AWS Region. e.g., us-east-1
No response
Other information
No response
The text was updated successfully, but these errors were encountered: