New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Best way to have persitent browser session accessible via browser?
hades_corps
Member
in Help
Hi,
As the title suggested, I have a few sites that need to be access from different devices. It also need to be keep alive while I'm not accessing it (not closed down and open again). Preferably with 2FA login, USB/PassKey pass through. I have a dedi running Proxmox to host VM if needed. I did not studied IT so please bare the novice questions.
So far I have a list of options and a few issues:
- KASM: I am still confuse about what it does. It looked like it suited for my need!? Does it keep the browser alive between login?
- Guacamole: It should fits but I am having issues connecting to it behind reverse proxy host by CloudPanel. Everytime it will says I'm disconnected. Could be wrong NGIX config?
- noVNC: No idea how to get it working, is there any 1-step install script?
- AnyDesk: With RealVNC changed their plan and TeamViewer agressive pricing (They also suddently think my 15-years account is cooperate account and disconnect every 5 mins), Any Desk should be a good free/cheap paid software? I still prefer being able to access via browser.
Comments
If you access it manually (by your self along with the device), how long does it keep logged in?
Basically, you're on right track. You can install either VNC or RDP and then open browser and it will keep connection alive. You can access it via other device using VNC or RDP client.
Or.. If the only way you can access it via browser then try this https://docs.linuxserver.io/images/docker-chromium.
All 3 mentioned KASM, Guacamole, and noVNC, are just webshells for your VNC server. Your question about keeping the browser alive is about VNC and X settings, not about the used webshell. So first of all, install the VNC server, test it with the VNC client, make port-forwarding rule in the firewall, and then decide if you need a webshell for it.