Hi, On Wed, Feb 10, 2010 at 07:19:52PM -0500, Ward Vandewege via RT wrote: > > Hi Sylvain, > > > [beuc - Wed Feb 10 14:11:21 2010]: > > Is there a problem with http://www.gnu.org/new-savannah-project/new.py ? > > Not as such - only with the access restrictions on it. They were still > set to the old Savannah - were you guys somehow routing all your traffic > through that box until we removed it yesterday?
Some of it yes - so that we could answer on the old IPs until the DNS propagation was done. > In any case, I've update the IP access list with the new IPs, so things > should be much happier now. It doesn't seem to work. You can test with: curl http://www.gnu.org/new-savannah-project/new.py -F type=gnu -F project=freedink curl http://www.gnu.org/new-savannah-project/new.py -F type=non-gnu -F project=dino Possibly you didn't include colonialone's IP (.51). Here's the list of IP adresses you assigned to Savannah: 140.186.70.51 140.186.70.70 140.186.70.71 140.186.70.72 140.186.70.73 140.186.70.74 140.186.70.75 -- Sylvain
