Will Netscape work?
MGoBlog vs. Internet Explorer (Technical Knockout by "nginx")
Mine is the opposite. I am able to get on MGoBlog through Internet Explorer, but not Firefox. I prefer Firefox so I am a little upset by this. WTF is going on and does anyone know if this "Welcome to nginx!" thing be fixed anytime soon?
Similarly, I couldn't (still can't) access through Chrome, but was able to access through IE. I've been having problems posting in the app on android. Everytime I comment on a thread the app closes.
situation with mine. No go on Chrome but I'm commenting with Safari now
several times on IE, but it's been fine since. Not being an engineer/technical whiz, wasn't sure it wasn't my computer that had been assaulted by a kidnap/hacker/virus thing. So is this perhaps a site invasion rather than a particular browser incompatability?
EDIT: See more knowledgable others below with had similar experiences. Also reminded me that I did do a cookie/cache clean-up, but I think that was later in the day after I was able to re-access.
I had to use port 8080 with IE10, due to the error fwiw...
I was having the same problem on chrome until it suddenly stopped, I didn't think to try a new browser... Are you certain that's what caused the issue for you? Like, even now you can access mgoblog by firefox but if you switch back to IE it doesn't work? Because I had assumed it was a server issue that would be common to all browsers.
Web browser wasn't the issue. Everyone was getting the nginx screen yesterstay.
It was doing this for me yesterday morning but doing a hard refresh (Ctrl + F5) fixed it for me.
Although you should really be using Firefox or Chrome over Internet Explorer anyway.
Thanks for the F5 tip. That helps. Now I can stop using this damn IE.
Just tried the (Ctrl +F5) trick and it worked for me on Firefox so everything is back to normal. Thank you so much for sharing this!
The "Hard Refresh" allowed access through Internet Explorer. But, you're right, MGoBlog works better with Firefox.
For a while, I thought that Edward Snowden (or maybe Vladimir Putin) might've been fooling around with my computer, now that Snowden has a little more "freedom" to play.
Thank you. I had no idea there was such a thing as a hard refresh - been using the soft F5 for last 15 yrs apparently.
it happens to everyone at one point or another.
They might testing the mythical "new mgoblog 3.0". I don't think it's a browser thing. It happened last weekend as well. App wasn't working either.
Happened on my app and from chrome a lot for me last week. Don't think it's just Internet explorer.
Nginx struck my iPhone OS too. No idea what's going on with that.
Had it on my Iphone 5, too. Powered it down completely and then powered up again. Everything back to normal.
Still uses IE
I haven't been able to get on for over 24 hours, until I just did a search for U of M Blogs and got this link: http://mgoblog.com/mgoboard and was able to get on for the first time. My old bookmarked mgoblog still gives "Welcome to nginx!". I use Firefox. The new content that I now get has most of the usual stuff, but also includes lots of historical sticky things. I was going through withdrawal because of not getting mgoblog anymore!
People still use Explorer?
I said this in another thread but what worked for me was clearing my browser cache. Fixed the problem instantly....and mine was a Firefox problem not Explorer.
What would be hardest to go without during football season: MGoBlog or alchohol?
If we're winning, Mgoblog. The Horror; alcohol.
That's just a horrible predicament. The first time someone comes to MGoBlog there should be an addiction warning you have to agree to. Like the alcohol company websites that ask you to verify you're over 21
Hmmmm... maybe I should lay off the MGoBlog.
Glenlivet MGoGrog Single Malt should work.
I don't really think it's a browser issue, but if this issue got people to stop using IE, then it was good for them.
So, raise your "hand" if you thought the site went down due to a high profile commit server overload.
Don't tease me bro.
lemme guess, you have a hotmail account too?
Chrome and the MGoApp have been working fine for me since yesterday morning. I was hoping it was because D. Hand committed and it caused an MGoMeltdown.
It happened on my chrome browser as well.
as another posted said, clear your browsing history. It has somehting to do with a stored cookie causing a redirect error.
I got the nginx screen for several hours yesterday with Safari and Chrome. Was hoping it was commit overload but no such luck.
I'll just keep using Iceweasel and Chromium.
ctrl + f5 worked for me on chrome. The nginx went away.
I just use the mgoblog mobile app!! (cmon elaydin you know you want to up vote this...)
Chrome and Internet Explorer work for me, but Firefox still doesn't. Which stinks because the fox is my main browser.
One of the guys in another thread suggested clearing out cookies and browsing history for the last few days (since the nginx error started appearing). That worked for me on Chrome. Before I did that, going directly to mgoblog.com/mgoboard allowed access to the website (but not the front page, even clicking on the banner).
I reset safari and the computer and that did it for me
Those are intermittent server issues, likely caused by an error on the hosting provider's end (e.g., mixed up DNS resolution). If you get the Nginx page once and continue getting it, it's because you're using a browser with aggressive caching enabled (especially Chrome, which can be a web developer's nightmare, but also Firefox, Opera, and maybe IE10), so do a hard refresh (F5 or Ctrl + Shift + R) to instruct the browser to skip the cached version.
Emptying the cache fixed it.
I'm having that problem with Chrome on my tablet. Not sure what the deal is.
Clearing browser cache, history and cookies should correct the problem. If it doesn't then it's a webserver configuration problem.
As far as I can tell this is an internet-wide problem (e.g. Yahoo was affected) for anyone who uses ngix servers. UMHoops was having problems too. Once it was fixed you had to refresh your cache, which most Web browsers will do automatically from time to time unless you use a particularly crappy web browser and never fixed its settings. MGoBlog will work on IE if you have IE working properly, however ysing IE as your main browser makes as much sense as walking around with a bag of rocks tied to every limb, except less because at least with the latter you get stronger. Use Firefox or Chrome or Safari; it'll be like internet without punching yourself in the dong every five minutes.
Do you have any news articles about this being an internet-wide problem? I wasn't able to find any newsy items and ngnix is know to be stable, which is one reason it's used by so many websites. Thanks Seth.
No news articles. When I was trying to do Dear Diary early friday morning I was having problems and went twittering. A few people up at that hour confirmed this was happening in various places; seemed to be done by 7:30 a.m. or so but the problems extended so long as people weren't clearing their cache.
who the hell still uses IE?
According to statcounter almost a third of the people in the US still use IE.
30.3% for IE
34.89% for Chrome
17.14% for Firefox
30.3% is pretty close to the elderly population of america
no love for Opera?
1. IE is still used by 90% of corporate America
2. Has tried using any version of IE in the past 2-3 years? IE 6=terrible IE 10= not so bad.
IE is used by 90% of corporate America because it's all run by the same family members you know who you tell "NO GRANDPA, CLICK ON CHROME". I work in corporate america, I extol the virtues of firefox and chrome whenever I get the chance
Keep doing that.
And how's that working out for you?
at least corporate america is embracing bring your own device and ditching those crappy blackberries
that whole Windows thing. No thanks, only when I have no alternative, and that seldom happens.
I'm glad someone posted this as I thought that the whole site had gone down. That being said, I'm still seeing the "nginx" screen despite resetting my iPhone 5. Desktop browsing is fine with Safari. Guess I'll have to use the mobile app instead for a while...
For Firefox go to the drop down, help, Troubleshooting information, reset firefox. That will fix it.
I had this problem with Chrome until I cleared all cache and cookies - at which point it immediately started working perfectly. Whatever the original problem was it was residing somewhere in the stored data.
Happened to me yesterday, couldn't access it at all! I closed out of the app, tried on safari, and reset my iPhone which didn't help. Finally at about 830ish when I checked for the umpteenth time it worked. I was checking the board diaries everything and nothing was working, thought the site was down or hacked or something hell idk
It was weird. I was able to get on with the wifes laptop but not mine. Your trick worked.
Mine wasn't working on Chrome at all. I typed in the full address (www.mgoblog.com rather than just mgoblog.com) and it worked just now
If you use IE, you probably aren't my friend.
If you use Opera, you're a hipster.
Opera is fucking awesome. Current builds of Next are based on the Blink rendering engine in advance of the complete switch-over.
Also, to play up the hipster part: Opera was touting open web standards before they were even standards.