Skip to content
Mason Sipe (school) edited this page Oct 1, 2018 · 6 revisions

Troubleshooting and Known Problems.


SSH

Cannot connect to 62111 or 22:

There is an issue that is known for ssh to not allow connections on port 22 or 62111 when the script finishes. This is because by default there is no rule to allow connections coming in from 62111. To fix this problem you need to run these commands:

  1. ufw allow in 62111 - If you know a specific host to allow into your system use allow in 62111 from (IP address)

  2. service ssh restart

  3. ufw enable

SSH is on and accepting connections on 22 or 62111 but netstat shows that there are no ports listening on either.

This issue is caused by a UFW being disabled or not allowing connections because rules have not been set. To fix this problem you need to enable ufw (ufw enable).


RecSetup

Kernel preventing UFW and APT to work:

Issues where you update your system then upgrade and suddenly your system will not allow any rules because you need to reboot. If this happens to stop the script immediately. Reboot your system with the reboot command and run the script again. It should work faster since it has fewer processes to run. This should cause the errors of the ufw and iptables to be fixed and should allow the other apt processes to work. The SSH error is adjacent to this error.


Clone this wiki locally