Open k3x opened 10 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
You need to configure Apache to be able to handle websockets which I would expect to be covered in kasm's docs. We can provide support using our swag reverse proxy(nginx) but not others.
None of us use Apache, if you figure this out feel free to update us with the fix, but I will not be spinning up an apache env to troubleshoot.
Thank you for your Feedback.
(see https://kasmweb.com/docs/latest/how_to/reverse_proxy.html#update-zones )
I got it working. Here some infos:
<VirtualHost *:443>
# Server Name
ServerName xxx
# SSL
SSLEngine on
SSLCertificateFile /etc/letsencrypt/live/xxx/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/xxx/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
# Proxy Settings
SSLProxyEngine on
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off
ProxyPreserveHost on
ProxyRequests off
# Websocket upgrade
RewriteEngine on
RewriteCond %{HTTP:Upgrade} "websocket" [NC]
RewriteCond %{HTTP:Connection} "upgrade" [NC]
RewriteRule ^/?(.*) "wss://127.0.0.1:8008/$1" [P,L]
# Proxy
ProxyPass "/" "https://127.0.0.1:8008/"
ProxyPassReverse "/" "https://127.0.0.1:8008/"
</VirtualHost>
Tagging WIP to keep open, until I can figure out a method of disseminating information like this to users.
You need to configure Apache to be able to handle websockets which I would expect to be covered in kasm's docs. We can provide support using our swag reverse proxy(nginx) but not others.
If you use Nginx, you can add two lines to handle websockets.
# WebSocket Support
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
See more in kasm's docs.
Is there an existing issue for this?
Current Behavior
I am running a server in my local network which has many services running in docker. I want to add Webtop:ubuntu-mate to these services. Here is my Docker-Compose File:
From my client in my local network i am Able to reach http://192.168.178.75:8007/ and https://192.168.178.75:8008/. Everything is working fine so far. Now i want to make this service available behind a reverse proxy. I used the documentation here: https://kasmweb.com/docs/latest/how_to/reverse_proxy.html#example-apache-config This is my Apache config:
The Documentation also mentions i should "Update Zones" in "Kasm Workspaces UI". How can i do this? How can i reach the Administrator UI?
I have a DNS-Record to my router which is forwarded (using NAT) to the docker host. Let's assume the DNS-Record is example.com. When opening https://example.com i see this:
Expected Behavior
The Desktop should be visible.
Steps To Reproduce
see Current Behavior
Environment
CPU architecture
x86-64
Docker creation
Container logs