That's a new one...
ERR_TOO_MANY_CONNECTIONS usually comes from the server, so the different behaviour from Chrome is rather odd; all I can think of is that one or the other has cached something.
Server-side, this comes from the database, which has a limit on how many connections it can accept at once. By default, this is further limited by the operating system. When we set up this server, we set relatively high limits, but it appears that they may not have taken.
I've checked that the OS limit is high enough not to be a problem, and have once again forced the database to accept a higher limit, with a modification to the config files hopefully ensuring that the setting persists this time.
If this doesn't fix it, I'd first suggest clearing your Chrome cache. If that doesn't do the trick, I'll need to schedule some downtime for a full server reboot.
My friend and I applied for airline jobs in Australia, but they didn't Qantas.