Kasm stuck on "Creating a secure connection - 100%" accessing through Cloudflare tunnel

The most likely cause is that your browser failed to establish the WebSocket connection needed to stream the session's audio and visuals, or there is a reverse proxy/firewall misconfiguration blocking Kasm's upstream protocols.

If you are accessing Kasm workspace through Cloudflare tunnel especially, then Kasm's internal proxy ports (eg. 30128) wouldn't be reachable because you are accessing the page through:

[Your browser] --https--> [hostname on Cloudflare:443] --cloudflare tunnel--> [Kasm host:port]

So if your Kasm host uses an internal proxy port like 30128, then your browser has no way of reaching it.

The solution is to disable the proxy.

  1. Go to Kasm's Admin panel
  2. Open Admin > Infrastructure > Zones
  3. Edit the default zone
  4. Change Proxy Port to 0 (zero)
  5. Save/Apply

Comments

Post a Comment

Popular posts from this blog

Proxmox VM PCI Passthru Error MSIX PBA outside of specified BAR

Proxmox VM PCIE Passthru Error  MSIX PBA outside of specified BAR I created a Proxmox VM created for LLM purposes, with a NVIDIA RTX 3060 allocated to it through PCIE Passthru, which there are plenty of literature about. Essentially, Enabled "above 4g decoding" in BIOS. Ensure "Re-size BAR Support" is Disabled in BIOS. In PVE host, blacklist the NVIDIA drivers to ensure it is not used by the host so that the GPU can be passed on to the VM. Create a VM which will use the host's virtual GPU as the primary display. While the VM is offline open Hardware to add PCI device, select the GPU with all functions etc. It worked smoothly with the NVIDIA RTX 3060. Then... Later I replaced NVIDIA RTX 3060 with a RTX 5060Ti, thinking that it should be a smooth upgrade because the new card is using the same PCIE slot & the VM would use the same NVIDIA driver,  Upon replacing the GPU though, the VM would refuse to start with the following error message: MSIX PBA outside of sp...
Read more

Open WebUI cannot see your models in ollama after upgrade

After upgrading Ollama & Open WebUI, my Open WebUI no longer displayed the LLMs in Ollama. Initially I thought it may be to do with the Open WebUI configuration issue so I fiddled around with the IP Addresses of the Ollama API URLs. Especially when I could still access the LLMs in Ollama via Terminal. But a quick search revealed that the most likely cause was Ollama only listening to the local loopback address (127.0.0.1), hence Open WebUI could not connect to Ollama API port. To do so, 1. run the following command in terminal sudo systemctl edit ollama.service 2. Add the following lines in the editor to let Ollama listen to any IP address on the machine [Service] Environment="OLLAMA_HOST=0.0.0.0" 3. Save and close the editor 4. Restart processes and ollama by sudo systemctl daemon-reload sudo systemctl restart ollama   Then the Open WebUI started to show the models available in Ollama.
Read more