- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
So, it seems like those entries in the NLB access logs without TLS cipher info and 0 bytes transferred might be failed or incomplete TLS handshake attempts from the EV chargers. It's likely that the negotiation to establish an encrypted session didn't go through successfully. This could be because of issues either on the chargers' side or due to misconfigurations.
Since restarting the chargers temporarily resolves the problem, there might be some intermittent issues causing TLS failures.
To research deeper into this, you can check out the AWS documentation for details on NLB access log fields. It could help you distinguish between incomplete connections and successful encrypted sessions.
Though AWS doesn't directly support packet captures, one option could be setting up a proxy or an intercepting proxy between the chargers and the NLB to inspect TLS handshakes. Tools like tcpdump on an EC2 instance could be handy for troubleshooting at the packet level.
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa