3 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
2
I don't think your listener on port 443 is setup correctly. I issued the following command and no SSL connection can be established.
# openssl s_client -connect sasivalec.com:443 -prexit
socket: Bad file descriptor
connect:errno=9
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 0 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
---
0
I don't wish this headache on anybydy :') As i'm new on the AWS console, i've been trying to enable my SSL certificate for quite some hours now. I've decided to swap strategy and i'll tackle SSL from within my ubuntu instance using "certbot" and "Let's Encrypt". It seems to be much easier, faster and free.
con risposta un anno fa
0
I have the same issue. I was able to setup the SSL certificate on the ALB port 443 however traffic is forward to process on port 80 ... researching further on this issue
con risposta 8 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
i've removed the certificate from AWS and i'll be handling ssl inside my ubuntu instance with certbot; i've been battling with the aws console for way too long