| Oct 17 - 21:24:00 |
|
| Post Reply | Post new topic | Page: 1  |
| Little yellow/red square in lower right of your browser | Started by: Squishy on Apr 29, '19 23:01 |
|
If you see a little yellow or red square in the lower right of you browser window, this is a notification that you are not currently connected fully to MR and you may miss notifications like flashes of your mail notification or blinks of your personals. Press F5 to reconnect, and that dot should go away, thus meaning you are now fully connected again. https://i.gyazo.com/269120813eaf887d20d8f795f79996f4.png is an example of the yellow square. If it persists, it means you may be having network issues somewhere between you and the server, these most often resolve themselves. |
|
| Report Post | Tips: 5 / Total: $100,000 Tip |
| Being on mobile do you have a fix for the yellow square? | |
| Reply by: Vincent-Ligambi at Apr 29, '19 23:18 | |
| Report Post | Tip |
| Reloading the page should reset the connection. | |
| Reply by: Squishy at Apr 30, '19 00:40 | |
| Report Post | Tip |
|
I don't ever actually remember seeing a green square, if I'm being perfectly honest. |
|
| Reply by: Prae at Apr 30, '19 03:04 | |
| Report Post | Tip |
|
The green disappears instantly, so you would never actually notice it. |
|
| Reply by: Squishy at Apr 30, '19 04:08 | |
| Report Post | Tip |
|
Did something change that has made this more frequent? I already knew what it meant, but since this post I've noticed it much more frequently than before. Previously I might go yellow if I went idle for about 20 minutes, now it seems to pop up yellow every couple of minutes and I am constantly refreshing. Any idea why? |
|
| Reply by: MGK at May 01, '19 12:32 | |
| Report Post | Tip |
|
Nothing has changed on our end, a fair amount of of the people who keep me in the loop as to their problem are near cloudflare locations that are experiencing issues. The problem lies with it being unable to maintain a solid websocket connection the whole time. (Consider it like buffering in a streaming movie... one blip for one second and it cause issues) We can become more aggressive about it trying to establish a websocket connection every time, but that will have unintended side effects. The shitty part is, your ISP only really cares about the first hop or two in their network - ones owned by them. Cloudflare only cares about the 2-3 in the middle which is owned by them. And while we care about all 17 hops it may take, we can only get our datacenter to look at the last 2, the ones in their network and under their control. That leaves a whole lot of companies along the way who don't give a fuck when a customer thats not theirs tries to reach out and alert them to a problem. If you are experiencing issues a lot, you could start off by trying to narrow down where the problem is so that you can figure out who can be notified. You would need to do a traceroute during the time theres an outage and figure out where that outage is during the time it happens, then depending on who is responsible for that section of the route, contact them. Because your path goes from you to other company to other company to other company to other company to cloudflare to other company to other company to us, its a different path that is taken than if I traceroute you, (Since its not going through cloudflares network) so I can't get the information on who is down along your way. |
|
| Reply by: Squishy at May 01, '19 13:37 | |
| Report Post | Tip |
| Post Reply | View All Threads | Page: 1  |
Minimum $20,000