Timeline for Did Mojave break SSH login?
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 18, 2019 at 15:11 | vote | accept | sam452 | ||
| Apr 17, 2019 at 15:49 | answer | added | Allan | timeline score: 1 | |
| Apr 17, 2019 at 0:42 | comment | added | sam452 | I should have thought to do this earlier: Boot into safe mode so that any third-party applications are not impacting this machine. SSH from remote to ssh -p 7219 sam@mycomcastip works as expected. Later in the day, the connection failed. With that info I can deduce that the new VPN client my customer switched to is impacting this path. If you can append to your answer I will accept it. Thx for helping to narrow the variables. | |
| Apr 17, 2019 at 0:28 | comment | added | sam452 | Yes, that makes sense. It's something else. Not the firewall, not Mojave. | |
| Apr 16, 2019 at 15:02 | comment | added | Allan | Also, if you can connect from another machine on the LAN, it can't be Mojave that's rejecting port 22. | |
| Apr 16, 2019 at 0:00 | history | tweeted | twitter.com/askdifferent/status/1117940680565895168 | ||
| Apr 15, 2019 at 23:07 | comment | added | Allan |
Issue the command ssh -vv -p xxxx sam@comcastip so you can the verbose output of the connection. Post the output to your question
|
|
| Apr 13, 2019 at 18:13 | history | edited | sam452 | CC BY-SA 4.0 |
Affirmed Mojave firewall is off
|
| Apr 13, 2019 at 18:06 | history | edited | sam452 | CC BY-SA 4.0 |
Added additional troubleshooting step which eliminates router firewall
|
| S Apr 11, 2019 at 7:05 | history | suggested | slm | CC BY-SA 4.0 |
cleaned up formatting text
|
| Apr 11, 2019 at 0:24 | answer | added | slm | timeline score: 5 | |
| Apr 11, 2019 at 0:14 | review | Suggested edits | |||
| S Apr 11, 2019 at 7:05 | |||||
| Apr 10, 2019 at 22:40 | history | asked | sam452 | CC BY-SA 4.0 |