Blocked by universities

[eric-burel]

Is your feature request related to a problem?

A beta user sent me this screenshot, when accessing nextpatterns.dev from a university network:

And also got this feedback: "whats more annoying is this site enables hsts (or whatever the header that means this site will always be https), this means that I have to check in different browser as otherwise it just says it failed to connect"

This is not Tutorialkit/Stackblitz/Webcontainer faults, but the thing is that tutorials are aiming learners and therefore university students.

Describe the solution you'd like.

Not being blocked in universites :')

Describe alternatives you've considered.

Well that's a difficult one, but could we figure alternate solutions? I guess Stackblitz is aware of such issues and may have palliative solutions?

Additional context

No response

[Nemikolh]

Hey thanks for opening this issue!

Oh this is really annoying that this gets blocked especially because this page content is eventually entirely served by a node server running in WebContainer. However to get there, the first page has to fetch and installs a service worker.

Do you know if stackblitz.com previews also get blocked? The domain for previews is slightly different and I'm wondering if they're also running into issues there.

We're aware of such issues but IIRC the only way this can be solved is to contact the University so that they update their allow list.

[Nemikolh]

Oh in case this is useful, the shape of the urls is always:

*.(local-corp|local-credentialless).webcontainer-api.io

[eric-burel]

Indeed the user cannot access StackBlitz on this network either

I think this would be worth adding to the troubleshooting section of webcontainers documentation? https://webcontainers.io/guides/troubleshooting By the way Stackblitz has a separate, maybe redundant troubleshooting doc that adds different tips: https://developer.stackblitz.com/platform/webcontainers/troubleshooting-webcontainers

[dagilleland]

@eric-burel - Question: Is this a block that affects students' personal laptops when they are on the school's network, or is it limited to school computers? And if it does affect students' personal laptops, is it only when they go through the school's public access point or through a student log-in access point?

[eric-burel]

I suppose it's happening at network level so it would affect anyone on the school network, I think the person who raised the issue was using is own laptop and I suppose a log-in access point, which is the usual setup in uni.