21 replies to this topic

[KrazedOmega]

Two different computers and three different browsers give me this.




It's been like this for a day and a half.

[IraqiWalker]

That means you are having trouble receiving replies from the site. Probably due to either server load on their end, or throttling on your end, causing many packet drops.

It has happened to me before, but it was mainly because of my own connection.

[Nightshade24]

Ditto, often happens when my internet is dying.

[KrazedOmega]

My connection seems to be normal. Everything else is working as usual.

I did just run a traceroute to 192.99.109.192 (which I believe is mwomercs.com) and over eleven hops I get time outs on the second and seventh ones.

I know very little about networking but I would assume something close to my end and closer to theirs are having issues?

[IraqiWalker]

KrazedOmega, on 22 August 2015 - 07:07 PM, said:

My connection seems to be normal. Everything else is working as usual.

I did just run a traceroute to 192.99.109.192 (which I believe is mwomercs.com) and over eleven hops I get time outs on the second and seventh ones.

I know very little about networking but I would assume something close to my end and closer to theirs are having issues?

Could be. It's also quite possible that those particular nodes have been programmed to not return UDP requests (traceroute runs through UDP, a protocol for communication). If you are getting the hops after them, things should be normal.

By the way, on the 2nd and 7th node, did you just get no response from them, or partial?

[KrazedOmega]

IraqiWalker, on 22 August 2015 - 07:11 PM, said:

Could be. It's also quite possible that those particular nodes have been programmed to not return UDP requests (traceroute runs through UDP, a protocol for communication). If you are getting the hops after them, things should be normal.

By the way, on the 2nd and 7th node, did you just get no response from them, or partial?

I ran the traceroute three times. The second node never had a response. Twice the seventh one had no response and once it had one of the three.

[IraqiWalker]

KrazedOmega, on 22 August 2015 - 07:33 PM, said:

I ran the traceroute three times. The second node never had a response. Twice the seventh one had no response and once it had one of the three.

Thent he second node is most likely configured to not respond to UDP calls. However, it seems the 7th one is actually having serious problems, either due to congestion, or damaged hardware.

[LORD ORION]

I'm having the same problem for the last week,

It doesn't always happen, but 75% of the time the site is not loading properly (I've tried multiple browsers and multiple DNS servers)

Every other site I visit works just fine, it is only the MWO site that is having this problem.

[IraqiWalker]

LORD ORION, on 24 August 2015 - 05:33 AM, said:

I'm having the same problem for the last week,

It doesn't always happen, but 75% of the time the site is not loading properly (I've tried multiple browsers and multiple DNS servers)

Every other site I visit works just fine, it is only the MWO site that is having this problem.

It's the MWO server that's the problem.

I've noticed that if I refresh a page, everything in it responds significantly faster than if I didn't.

[KrazedOmega]

I'm still having problems. I dug a little deeper and looked into the locations of all the hops in the traceroute I ran. It all seems like a logical route until the seventh hop where it jumps from Toronto to...somewhere in Kansas...to the server in Montreal.

I guess I'll have to email support and see what they have to say.

[Tarogato]

This is happening to me, too. I know it's not my end, the rest of the internet is loading just fine and dandy when it happens.

[sycocys]

Been early morning (Canadia time) for the past 3-4 days like this for me. Solves itself by the afternoon.

[Mawai]

I have the same issue. It is intermittent and MWO is the only site affected so far.

It occurs using IE, Edge, Firefox or Chrome on Windows 10, WIndow 8.1 and Linux. The problem sometimes fixes itself with either a browser restart or a page reload but this is not reliable.

I have a 35ms ping to mwomercs.com

Ping statistics for 192.99.109.192:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 120ms, Average = 31ms

Running 100 pings shows no packet loss and an average ping of 31ms but the website was STILL messed up despite navigating and reloading the pages using various browsers. However, it was eventually able to load properly in Edge and Chrome after some page reloads and it did work in Firefox after closing and restarting the browser.

It seems to me that it is likely a network issue at PGIs end that needs to be evaluated.

[IraqiWalker]

For what is probably not the last time: it's on their end.

[Lily from animove]

try to add https:// in front of the page and see if it stays.

some time ago this happened way more often on the forum. It was related to some browsers somehow not supporting https (switching back to http mode and interpreting styles incorrectly)

maybe update your browser.

[Mawai]

Lily from animove, on 26 August 2015 - 06:36 AM, said:

try to add https:// in front of the page and see if it stays. some time ago this happened way more often on the forum. It was related to some browsers somehow not supporting https (switching back to http mode and interpreting styles incorrectly) maybe update your browser.

Well I have the issue with the latest versions of Chrome, Firefox, IE and Edge under Linux, Windows 8.1 and Windows 10.

Swapping https for http does result in the web page displaying correctly. Going back to http returns to the incorrectly displayed page (on Chrome, Edge and Firefox). I will start using https and see if the problem develops using the https connection after a while.

The website is much less usable when displayed incorrectly. I do think it is likely an issue with the website or the servers, they just need to acknowledge and fix it.

[Bobby Jubraj]

Hey guys,

We've looked into this and were able to fix the problem that was affecting some of our users when trying to access our site. Really sorry about that everyone and if you continue to have issues with our site moving forward, send me a message over at technical@mwomercs.com and I'll make sure to get back to you as soon as I can.

[Kyle Polulak]

Yup, it was our problem. Our CDN had cached empty CSS/JavaScript content and was serving that instead of the actual files (hence the no style and reduced functionality).

I have pushed a request out to fix it however a CTRL+SHIFT+R (CTRL+SHIFT+F5) to force clear your local cache in your browser might be required if you locally cached the empty files.

[Iqfish]

Pressed the button combination. Let's see how it works, thanks for the effort!

[IraqiWalker]

Bobby Jubraj, on 26 August 2015 - 10:43 AM, said:

Hey guys,

We've looked into this and were able to fix the problem that was affecting some of our users when trying to access our site. Really sorry about that everyone and if you continue to have issues with our site moving forward, send me a message over at technical@mwomercs.com and I'll make sure to get back to you as soon as I can.

Kyle Polulak, on 26 August 2015 - 10:57 AM, said:

Yup, it was our problem. Our CDN had cached empty CSS/JavaScript content and was serving that instead of the actual files (hence the no style and reduced functionality).

I have pushed a request out to fix it however a CTRL+SHIFT+R (CTRL+SHIFT+F5) to force clear your local cache in your browser might be required if you locally cached the empty files.

Thank you both, and hopefully this'll work out.