Terrible service with Forge after having more then 25 servers with them i stop using forge

@theProfit be civil

@theProfit yes, maybe not as polite as it might have been, but it still doesn’t warrant you saying fuck you.

@Tray2 Maybe, but i personaly hate people like @lumethys how bully people on there english, only save behind a screen..... but moving on.

i have made a script witch ads the missing ip's to the servers, you must login with SSH and then run :

sudo iptables -A ufw-user-input -s 159.203.150.232/32 -p udp -m udp --dport 22 -j ACCEPT
sudo iptables -A ufw-user-input -s 159.203.150.232/32 -p tcp -m tcp --dport 22 -j ACCEPT
sudo iptables -A ufw-user-input -s 159.203.150.216/32 -p udp -m udp --dport 22 -j ACCEPT
sudo iptables -A ufw-user-input -s 159.203.150.216/32 -p tcp -m tcp --dport 22 -j ACCEPT
sudo iptables -A ufw-user-input -s 45.55.124.124/32 -p udp -m udp --dport 22 -j ACCEPT
sudo iptables -A ufw-user-input -s 45.55.124.124/32 -p tcp -m tcp --dport 22 -j ACCEPT

If you do this forge will be conected again, but i think it is a big bug, because forge has the 3 remaining ip's and can only connect when you have all six of them, witch is a flaw if there is a DDOS attack to some of them you can't do anything, i would say use round robin. but i hope somebody has something about this script.

if you dont have a own ip added to forge you have a problem, so does everybody when there is a ddos on the 6 forge ip's so therefore i think it is bad.

@theProfit You are allowed to hate anyone you like, as long as you keep a civil tone on here, even when someone is being an ass hat.

I suggest sending a ticket to the forge support team regarding your issue. If it has to do with something in the documentation you can create an issue or an pr on the forge.docs repo on GitHub.

@tray2 problem solved was a bug, old ip's have been removed and where still on the site, problem fixed after some chats with them, best answer goes to @lumethys for his good attention and rapid fine comments! ;) Problem solved!

@theProfit you come in here with hostile attitude and a big rant with broken english. You expect a warm welcome with that type of attitude?

Furthermore, Forge's own doc say pretty clear that you must allow all of their IPs and they will change periodically: https://forge.laravel.com/docs/1.0/introduction.html#forge-ip-addresses

If you do not pay attention to the manual, do something wrong, then proceed to do a big rant as if it was someone else's fault, then do you really deserve a warm welcome?

You reap what you sown

as the saying go, be civil first if you want people to be civil with you

@theProfit Was looking for an UFW way as Forge servers get set up with it but perhaps I will need to use iptables directly to solve the issue with new ip address. Opened my own thread on this earlier https://laracasts.com/discuss/channels/forge/error-500-on-forge-ssl-crt-installation

@rhand happy to help, i was thinking about making a script to get the ip's from https://forge.laravel.com/ips-v4.txt, spoken to Guus from Forge and the first ip's of the txt are not in use anymore that was the problem they never said the first go out of business. But want to make a Recipe in Forge.

So my way was this:

// getting the txt file from forge.
// adding own company ip ranges (optional) 
// setting all open ports to close 
// adding ip's to DB of forge under network.

i am making it into a script once i have it i will post it here, also @rhand once you have added the ip's and you go to Forge GUI under network you can add them in there so it will show there later so you dont have to always check iptables. i will also ask them witch command there is to add them to the GUI (DB).

this will then be a default auto installer script for new servers and periodic to update the servers if there is a new ip. would be nice if Forge has made them own litle script like this.

i also think more people will face this problem in the next coming months because they disabled the first servers.