Yet here I am, using it on my desktop just fine. They're both running off the same wi-fi network too.
As usual, I have no idea what's going on . . .
The site's been mega-boned for me over the last 2 days. I don't know why this time it works. EDIT: When I type "hubski.com" into the address bar by itself it doesn't work. When I type "https://hubski.com" manually, it works. ????
Which phone are you using? Which browser? and if you know which version of browser and OS might be helpful too. Edit: The site is loading ok for me. I'm on an iPhone 6 iOS 8.3(12F70) using Safari (I can't find a version - I think because it is bundled with the OS)
mk, forwardslash, insomniasexx Anyone else having this?
Hey, sorry for the late response. I literally had to leave for work five minutes after posting this and I just got home. I'll tag mk, forwardslash, and insomniasexx, so they'll see this too. I've been experimenting with my phone all day so I can give you as much info as possible. I have no way of transfering screen shots from my device, but what the 503 error says is . . . Service Unavailable Guru Meditation: XID: XXXXXXXXX Varnish Cache Server The XID goes up by 2 digits every time I refresh the page. This shows up no matter where I'm pulling my internet data from, if I clear out my cookies, or even run in incognito mode. The crazy thing is, if I go to https://www.hubski.com it comes up just fine. It just has a problem with standard http web address. This fact remains true whether I use Chrome or the Generic Internet App. I'm running a Galaxy 4 with Android 5.0.1. This also happens even if I request the desktop version of the site. This all started today. No problems until now. I'm not complaining. I just thought I'd share.Error 503 Service Unavailable
It looks like for some reason our varnish cache server is caching a 503 response. When you go to https://www.hubski.com it bypasses the cache and goes directly to live data, so that's why it works. Hopefully restarting our cache server will fix it; let me know if it doesn't.
It's still pooched for me when I do it the usual way.
Aha! I figured it out. When I migrated our servers I didn't change the ip address in the cache configuration files, d'oh. Should be good now.
Nope. Maybe he's trying to pull the mobile session of the site?