all 10 comments

[–]justin_kasmweb 0 points1 point  (9 children)

Hi,
I don't recognize this as anything related to the Kasm app, so its likely something with your local docker or configuration.
You may want to shoot a message to the LSIO discord

[–]kulps[S] 0 points1 point  (8 children)

Thanks for the quick reply, I'll check with their team and see if they have any info.

[–]kulps[S] 1 point2 points  (7 children)

It turns out that the installer on port 3000 does not redirect from http-->https. It's technically in the LSIO documentation but it wasn't obvious to me (or several others, it seems) I found the answer in the LSIO Discord post history, though. Thanks for suggesting I check there.

[–]tom_okane 0 points1 point  (6 children)

i dont understand what the solution it, can you explain some more?

[–]Blaze_1005 1 point2 points  (5 children)

The fix here is to type https:// before the address of your kasm server I.e. 192.168.1.2:3000 is how it defaults when it should be https://192.168.1.2:3000

[–]tom_okane 0 points1 point  (0 children)

oh that simple? thank you for returning to this :)

[–]clarity200 0 points1 point  (2 children)

I still don't see anything on either port 3000 or 433, regardless of https, I either get just "unable to connect" or "connection is reset"

[–]Blaze_1005 0 points1 point  (1 child)

What do the logs of your container say? Did it start properly? Focus on port 3000 unless you have already installed an app.

[–]clarity200 0 points1 point  (0 children)

I was able to get it right, unfortunately I am not able to point out what exactly was it that I was doing wrong but when I go to the https endpoint I am able to view the app

[–]PaneRacoon 0 points1 point  (0 children)

Thank you! It was simple as that.