kasmtech
Client is unauthenticated - multiple IP's on manager/api host
Existing Resources
- [ ] Please search the existing issues for related problems
- [ ] Consult the product documentation : Docs
- [ ] Consult the FAQ : FAQ
- [ ] Consult the Troubleshooting Guide : Guide
- [ ] Reviewed existing training videos: Youtube
Describe the bug Agent is viewed as unauthorized when upstream proxy has multiple nics
Currently have a single server install on a PC (bare metal Ubuntu 22) as a kasm host,with a VM running elsewhere that i am trying to add an agent to the existing install. it will not ever send the session video feed. the session is created just find but never returns to the client. it just times out and goes back to the admin console. no error shows up in the error dashboard either.
The agent responds with heart beat etc all is well. but sessions started on the second agent do not get displayed to the client. reading the logs on the second agent machine (/opt/kasm/1.14.0/log/nginx/error.log) is showing the connected client as unauthorized. its showing it as the second nic
Kasm is setup with DNS name of manager/app (single server install) resolving to 192.168.1.10 (23bit subnet) second nic in this machine resolves to 192.168.1.185/23
2023/08/22 11:13:52 [error] 9#9: *27 auth request unexpected status: 404 while sending to client, client: 192.168.1.185, server: ubuntu-base, request: "GET /fdc47055-2025-40/45664601-e462-40de-840e-ed8c1a9ca723/vnc.html?video_quality=2&enable_webp=false&idle_disconnect=20&password=&autoconnect=1&path=desktop/720bcc6d-e852-4809-a468-7c9c39c042d3/vnc/websockify&cursor=true&resize=remote&clipboard_up=true&clipboard_down=true&clipboard_seamless=true&toggle_control_panel=false HTTP/1.1", host: "192.168.1.10", referrer: "https://192.168.1.10/"
I tried adding the the IP to the host file of the machine to see if it resolves it as the same host but it does not. I cannot disable the other nic as its hosting other services. but i fell that would be the quickest way to solve the problem
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Workspaces Version Version 1.14
Workspaces Installation Method Single Server, migrating to Multi-Server (is that even possible ? )
Workspace: Kasm Chrome workspace - restricted to the second agent server
Sorry i did a really terible job of describing this issue, the second agent machine is stating that the kasm host is unauthenticated not that the client is unauthenticated.
Sorry for the late reply. It sounds like you had a single server, and you wanted to add another agent to it. Unfortunately thats not a supported architecture, and would result in the sessions not loading for the end user like you saw.
The options are single server and multi-server: https://kasmweb.com/docs/latest/install/multi_server_install.html
