Hi. (probably not playcanvas-related?)
I’m having problems reaching playcanvas.com in Chrome on Windows and Mac. Firefox on the other end works fine.
On chrome I get this message. Anyone with a clue on where this could be hindered?
Happy holidays!
Hi @bjorn.syse,
Seems to be working now for me.
I got that error a couple of days ago for a few minutes while the team was deploying some changes.
I see. I’ve had it for weeks now. It’s trange it only affects Chrome, but I can access login.playcanvas.com and my editor and projects.
Maybe try clearing your cache and cookies for PlayCanvas. Com in chrome?
I’m afraid not. Hard reload, emptied cache, deleted all related cookies. Nothing seems to helt there.
Strange, does this happen in incognito mode too?
Yes is does.
Very strange, it seems to be referring to this bug: 1173575 - chromium - An open-source project to help move the web forward. - Monorail
Does it happen with Chrome on another PC on the same network (if you have access to one)
It’s crazy I know.
It happens on my macbook using chrome too on the same network. Also if I tether via my phone.
Are your devices owned by a company? Do they control chrome on any way?
Hi again
Yes, the windows-chrome instance is indeed controlled but I’ve double checked the chrome://policy/ and I see no policies that would block certain domains or so set.
The Macbook-chrome instance is not controlled and shows the same behaviour.
Not sure what could be causing the issue besides the network 
Can you paste this on your Mac terminal please:
traceroute playcanvas.com
And send me a DM of the output please?
Good idea, here is the output from Macbook. Issue is present in Chrome aswell as in Safari).
Bjorns-MBP:~ bjorn$ traceroute playcanvas.com
traceroute: Warning: playcanvas.com has multiple addresses; using 54.230.99.118
traceroute to playcanvas.com (54.230.99.118), 64 hops max, 52 byte packets
1 openwrt (192.168.1.1) 39.141 ms 8.328 ms 11.270 ms
2 gw13-no70.tbcn.telia.com (194.17.165.129) 15.407 ms 5.631 ms 16.506 ms
3 ksn2-c2-link.se.telia.net () 27.288 ms * 16.950 ms
4 * * *
5 hy-peer1-link.se.telia.net () 30.057 ms * 32.306 ms
6 s-b2-link.ip.twelve99.net () 12.756 ms * 52.250 ms
7 amazon-ic325291-s-b6.ip.twelve99-cust.net (62.115.155.153) 25.053 ms 26.641 ms 13.152 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 server-54-230-99-118.arn1.r.cloudfront.net (54.230.99.118) 6.721 ms 7.957 ms 10.201 ms
This is the same traceroute on windows machine where Chrome can not reach playcanvas.com, but forexample Firefox can.
C:\Users\tmgxbs>tracert playcanvas.com
Tracing route to playcanvas.com [54.230.99.62]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms OpenWrt.lan [192.168.1.1]
2 2 ms 2 ms 2 ms gw13-no70.tbcn.telia.com [194.17.165.129]
3 5 ms 6 ms 5 ms ksn2-c2-link.se.telia.net []
4 * * * Request timed out.
5 * 5 ms * hy-peer1-link.se.telia.net []
6 5 ms 5 ms 5 ms s-b2-link.ip.twelve99.net []
7 9 ms 11 ms 9 ms amazon-ic325291-s-b6.ip.twelve99-cust.net [62.115.155.153]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 5 ms 5 ms 5 ms server-54-230-99-62.arn1.r.cloudfront.net [54.230.99.62]
Trace complete.
I’ve removed your private IP addresses just in case 
It’s really weird since it is accessible from the network you are on and via Firefox. Honestly we are at a lost on why Chrome specifically can’t access it .
Could you try Edge or Brave browsers as they are both Chromium based to see if it has the same issue please?
Ah, thanks!
Edge on my windows machine will give me this on www.playcanvas.com
However, playcanvas.com without www is accessible. That is not the case for chrome though.
Perhaps this is something in my personal LAN router that needs flushing?
Oooooh, interesting that www.playcanvas.com is not accessible. Great find, thanks!
That I can reproduce locally so I ask our infra team to look into it.
It’s fixed now, thanks for reporting!
Great, what in the world was that? Howcome it did not affect all of us, and not all browsers?
Just to check, is everything working for you?
