When adding first instance on a new session (Chrome), the terminal does not appear.
PSUHammer opened this issue · comments
In Play with Kubernetes Classroom I am unable to see the command line in Chrome. No ad blocker enabled. Tried resizing window.
Google Chrome is up to date
Version 72.0.3626.109 (Official Build) (64-bit)
Also, in the lab (play-with-k8s) I am unable to add an instance as clicking that button does not bring up the terminal window.
Same here, go to https://labs.play-with-k8s.com, click "Add new instance" buttton : nothing happen
Error displayed in chrome debug console :
Failed to load resource: the server responded with a status of 500 ()
Same as above, Firefox 68.0 (Fedora 30).
Same issue on MacOS Chrom Version 76.0.3809.100 (Official Build) (64-bit)
I am having the same issue using MacOS 10.14.5 and Chrome version 76.0.3809.132 (Official Build) (64-bit).
Guys can anyone respond on these queries..I am also facing issue..tried adding instances at the left side but nothing happening on the screen finally end up with time out for the session
Same issue,
the problem had made progress?
POST https://labs.play-with-k8s.com/sessions/bvqblg6j2b7000dm9kq0/instances 500
(anonymous) @ angular.js:11756
m @ angular.js:11517
g @ angular.js:11227
(anonymous) @ angular.js:15961
$eval @ angular.js:17229
$digest @ angular.js:17045
$apply @ angular.js:17337
(anonymous) @ angular.js:25023
dispatch @ jquery-3.2.1.min.js:3
q.handle @ jquery-3.2.1.min.js:3
Same issue, I use Edge, it works. And when I go back Chrome, it works too.
I don't know why.
Try opening the playground on one browser and click on new instance, that probably won’t show anything. Then open the playground on another browser. It gave no error and provided with a terminal.
On Firefox.
Then on chrome
I don't understand what is causing this. Appreciate if anyone can figure out the explanation.
Hope this method compensated.
THX.
Original Message:
For chrome users: click on the padlock in the URL bar --> Site Settings --> Permissions --> change Pop-ups and redirects to "Allow".
NB: This only applies to https://labs.play-with-k8s.com/ - so all good there, and seems to resolve the problem, at least for me.
Update:
It seems to be an environmental issue. After resetting the first-session once again i face the same problem.