Our municipality is attempting to open up the firewall for all the makecode editors on the student chromebooks on our school.
However, even though they get “Successful” for all domains that the @makecode team specifies must be reachable according to e.g. https://arcade.makecode.com/domains, the simulator is not loading, only showing blank with about it not being allowed by the organization.
Are there any other domains or settings/functionality(e.g. scripts/languages etc.) that are needed for this to work?
The simulator runs from https://trg-arcade.userpxt.io/---simulator (from that list), so should be good – are you able to open up dev tools (I believe ctrl+shift+i or F12 should typically still be allowed) in case there are any other errors?
Only things that’s more specific to that domain is that it’s used in an iframe / cross origin in the page; in theory could be some settings for that (e.g. ad block or something?) but would be a bit surprised.
I’ve forwarded your suggestions about iframe /cross origin to the IT department, but unable to check again on the student’s chromebooks until next week.
@richard: Did you get any useful data points you could share in this analog case with all required domains reachable, but the simulator still not loading?;
Wish you all a great weekend on the other west coast (already weekend here…)!
nope, still a mystery for me. is it possible that the domain is unblocked but the specific url is blocked? i’m not super familiar with how these block lists are structured. does going directly to that link that @jwunderl posted work? https://trg-arcade.userpxt.io/---simulator
The IT dep. is informed about this thread, and the last thing I read in my open case is that they had allowed for a couple of additional addresses and that I should test again on a student’s chromebook as soon as possible.
If now solved, I’ll try to query them about what the issue was in addition to your listed domains and post back here. Maybe we then will discover a common denominator, if there is one.
I am sorry, but it slipped my mind to test the specific address you provided, https://trg-arcade.userpxt.io/---simulator, in the beginning when the IT department had only opened for https://trg-arcade.userpxt.io/ etc. as noted in your Arcade reachable domains list. So I cannot ascertain whether the —simulator part was specifically added later and makes a difference or not.
There were no challenges with iframes or cross origin, according to the IT department. In addition to the editor specific trg-arcade.userpxt.io, trg-microbit.userpxt.io, trg-ev3.userpxt.io etc. which appear on your various reachable domains lists, there was one additional address which they had to open up for to get the simulators to load and that is not on any of your reachable domains lists: pxt.azureedge.net
Does this make sense and should the latter domain be included in all your reachable domains lists to ease the traversal of local firewalls for others in the future?
hmm, that’s a domain we used to use but i don’t think we do any longer. maybe it was tripping up an old version of the service worker for the simulator that was cached…
I have no idea, just reporting back an address which is not on any of the reachable domains lists and that the IT department claims had to be opened for in addition to get the simulator working across the various editors (arcade, micro:bit and mindstorms), and hoping to reach a conclusion to this matter that may help others. Perhaps pxt.azureedge.net only applied to the older mindstorms editor, and that they did not manage to open all the other addresses in the reacheable domains list when they attempted the first time and the simulators across all editors were still not working.
