Can you elaborate on the issue please? Were there any error messages? What steps did you take to access the shell?

Based on your location it looks like this is on a self-bootstrapped controller. Have you deployed the juju shell charm and pointed the GUI to it?

I am getting this as well. In my case I deployed K8s core with juju. In addition I threw in the jujushell charm and exposed it. I clicked on a button to execute a post-deployment script, and oopsie.

Ahh ok, so using your own juju-shell charm with the GUI hasn't ever really been thoroughly documented. We are planning on making this experience a lot easier with the new Dashboard that will be replacing the GUI in the near future.

What you'll need to do is press shift+1 to open the settings menu and in there you'll see an input for the DNS name for the juju shell. Setting this value will override the default, which on a self-bootstrapped controller is empty.

This is the jujushell charm: https://jaas.ai/u/juju-gui/jujushell and as you'll be able to see there are a number of configuration options that you'll have to set to get the best experience in your environment.