Ping Works, but HTTPS Doesn't: How to Find What Actually Broke

Описание и применение

Успешный пинг не гарантирует работоспособность HTTPS. Пошаговый подход к проверке каждого уровня сети (ICMP, DNS, TCP, TLS, HTTP) позволяет быстро определить точку отказа.

Задача

A successful ping does not guarantee that HTTPS traffic will work, leading to misdiagnosis of network issues.

Результат

By testing each network layer separately, the first point of failure is isolated, reducing troubleshooting time and avoiding false assumptions based on ping success.

Рабочий процесс

• 1. Verify ICMP connectivity with ping.
• 2. Check DNS resolution using dig or getent.
• 3. Test TCP connectivity to port 443 with nc -vz or curl -v.
• 4. Inspect TLS handshake with openssl s_client or curl -v.
• 5. Verify HTTP response with curl -v.
• 6. Test proxy paths with curl --noproxy and environment variables.
• 7. Check for Path MTU issues with traceroute or mtr.
• 8. Use Network Doctor (netdoc) to automate the steps and summarize results.

Доказательства

Ping normally uses ICMP echo requests and replies.

A successful ICMP echo doesn't prove all of those layers work.

You can test it directly: nc -vz example.com 443

openssl s_client -connect example.com:443 -servername example.com

netdoc example.com

Источник