Troubleshooting

Fix: ssh: connect to host github.com port 22: Connection timed out

Fix: SSH Port 22 Timeout title over a silhouetted figure holding a light before a sealed dark gate while a glowing orange path curves around it to a bright citadel.

Your network blocks SSH on port 22, not your key. Route GitHub over ssh.github.com on port 443, make it permanent in ssh config, and verify with git.

Fix: Support for Password Authentication Was Removed

A terminal showing a git push rejected because password authentication is not supported.

GitHub rejects your Git password over HTTPS. Switch the remote to SSH, or create a personal access token and store it, so pushes stop asking.

Fix: Too Many Authentication Failures

Fix: Too Many Auth Failures title over a silhouetted figure holding one glowing key before an arched gate lit by a column of lights, a huge ring of keys beside them.

SSH offers every key you own and the server cuts you off after six. Pin one key with IdentitiesOnly, and learn why GitHub gives a different error.

Fundamentals of Software Debugging

Abstract illustration of software debugging workflow: define failure, reduce surface area, form hypotheses, collect evidence, confirm root cause, and prevent recurrence.

Software debugging fundamentals for developers: mental models, evidence-driven workflows, observability signals, and practical techniques for finding root causes fast.

Fix: Push Declined Due to Email Privacy Restrictions

GitHub rejects the push because your commit email is private. Set the GitHub noreply address, repair the commits you already made, and push again.