When you accidentally block Forge from your server.... 🤦♂️
November 28th, 2020 - 1 min read
Heads up! This post was published a while back, so while some of it might still be good, I can't say for sure it's all accurate. Take it with a pinch of salt!
I did something a bit stupid yesterday... I was playing around with Firewall rules on my Forge server. I setup a rule so that the only place I can SSH into my server was from my home IP Address.
However, as soon as I did that, I realised that I could not longer deploy code or do anything via Forge on that server. Then I realised my mistake.... I blocked Forge's IP Address from SSH'ing to my server.
In case someone else finds them in my position, here are the two commands I ran to fix the issue. Of course, you need to SSH to run them.
1sudo ufw allow from 126.96.36.199 to any port 222sudo ufw allow from 188.8.131.52 to any port 22
ufw under the hood to manage firewall rules so that's what I used to manually give Forge back control. The two IP addresses I listed in those commands link up to the IP addresses from their documentation.