Here's the situation with the web chat.

Previously, the web chat ran from a server at my house.  When I shut down our liquid web server, something happened and no one could connect to my at home chat server anymore.  The at-home chat server ran on chat.gcworldind.com and used a free startssl SSL Cert.  This had been operational for a very long time and functioned perfectly.

Once that broke, for whatever unknown reason that may be, I fired up a new server at our new hosting provider and installed ejabberd.  The server itself is functioning properly.  It's running on chat.konghack.com.  We have a full Wildcard SSL Cert, which I've installed into the server.  ejabberd uses a fucked up PEM file for SSL.  This PEM file is our cert, our private key, and an "intermediate ca" cert.  I've added all 3 to our pem and rebooted the server.  Apparently it's still not functioning correctly.  I've tried every cert labled as an intermediary cert in the godaddy cert repository.  No fucking luck.

I've wasted a fuck load of time on this and still can't get it working.  It is a SSL cert issue.  I don't want to hear any other bullshit about COR, http-bind, etc.  It took me a few hours to get SSL working on the old server, and as soon as I got it working, BAM, we were in.  When connecting from PSI, guess what?  SSL issue.

I'm giving up and moving on for now.  I have 2 kids to take care of and thousands of little fires that need to be put out.  If you want to chat with us, go download a client and connect in.

You can find the connection info by going to UCP > Chat Info, or using this link directly: https://konghack.com/ucp/xmpp

Good luck.

I'm still working on it.  Everything else seems to have died down.

Check this shit out:
 openssl s_client -connect chat.konghack.com:5222 -starttls xmpp </dev/null

Run that in either a fully loaded cygwin or via terminal in linux.

UPDATE: I switched out the intermediary cert for the ga bundle, different response, now it's showing a self-signed cert is in the mix.  Still no fucking idea...

Update 2: Ok, threw both intermediary certs on the end of that.  It's now showing 6 valid certs in the server.pem, and sitll nothing is fucking working.

At least you're an inspiration of hard work and entrepenureship.

I contacted their support and that was their response.  They won't even sell you an SSL cert for a domain with hack in it.  You have to go somewhere else. :P
Anyway, Kolonel's working on an IRC thing I think.  I hooked him up with a server to play with. :D

lmfao, the chat server never broke 0.02% load.  it's a dual socket quad core with 16GB ram.  We've never had more than 30 people in chat.  Yeah, so much stress.

I did find the issue with the old chat server.  I'm certain it's a DNS issue, since that's what caused a ton of problems to begin with.  I'll work on it tomorrow.  My youngest is still sick. :(

Chat's back up.  CURL didn't like our new SSL cert, so with a little fucking around, I got the old box back up and running.  We're still on the basement beast. :P