Hi There, I've tried connecting on multiple computers, and on Chrome/IE/Firefox (main browser is Chrome). I am told by my friend that the server is online. Here are the details of my problem: Error: "Card Hunter is currently down for maintenance. Please Try Again after a few minutes." Chrome Version: 27.0.1453.116 m Javascript Console: Viewport target-densitydpi is not supported. payments.html:4 XMLHttpRequest cannot load http://live-server.cardhunter.com:8080/check_maintenance.jsp. Origin http://live.cardhunter.com is not allowed by Access-Control-Allow-Origin. live.cardhunter.com/:1 I have asked about the ports, and 8080, 9933, and 8443 are all open. Any suggestions would be greatly appreciated.
I think I've encountered the same issue. The Viewport message in the Console seems to be just a warning. The actual error (about crossing the origin boundaries) on my machine shows as: Blocked a frame with origin "https://checkout.google.com" from accessing a frame with origin "http://live.cardhunter.com". The frame requesting access has a protocol of "https", the frame being accessed has a protocol of "http". Protocols must match. Source reference are: payments.html:1 (anonymous function) payments.html:1 (anonymous function) frame.js:1 I trtied disabling AdBlock but that made no difference. HTH
I had posted previous that I was told those ports were open. (I'm at work ) And it wasnt working. So I decided to create a hotspot from my phone. Tried connecting through that, and it worked just fine. So this had to do with the network at my work. Sorry about this! Interesting note: After I used my phone to create the hotspot to load the login page. I turned off my phone and connected back to my work Wifi. Then figured "what the hell" and tried to log in. And it worked! I'm actually playing currently. So I guess I just needed to bypass connecting aspect of the login screen, and I was able to play.
Glad you got it working! That XMLHttpRequest error is one I thought we'd resolved months ago, but apparently there's still some network configuration that causes it despite our server setting the Access-Control-Allow-Origin header to "*". I wonder if your work network is sending you through a proxy that filters some headers from the response.
