Difference between revisions of "ESXI - WebUI Through a Proxy"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
Apparently, Console sessions use WebSockets. | Apparently, Console sessions use WebSockets. | ||
| − | This turns out to be fairly simple to solve. | + | This turns out to be [https://communities.vmware.com/thread/595344 fairly simple to solve]. |
If not already there, you'll need to enable the ws_tunnel module on your proxy server: | If not already there, you'll need to enable the ws_tunnel module on your proxy server: | ||
| − | * <code>sudo a2enmod proxy_wstunnel</code> | + | *<code>sudo a2enmod proxy_wstunnel</code> |
Then add the following to the <VirtualHost> block for your ESXi Server: | Then add the following to the <VirtualHost> block for your ESXi Server: | ||
| Line 17: | Line 17: | ||
and restart Apache: | and restart Apache: | ||
| − | * <code>sudo service apache2 restart</code> | + | *<code>sudo service apache2 restart</code> |
Latest revision as of 13:23, 24 June 2020
When proxying ESXi through Apache, VM consoles fail...
Apparently, Console sessions use WebSockets.
This turns out to be fairly simple to solve.
If not already there, you'll need to enable the ws_tunnel module on your proxy server:
sudo a2enmod proxy_wstunnel
Then add the following to the <VirtualHost> block for your ESXi Server:
# Redirect wss traffic ProxyPass /ticket/ wss://ESXiServer.MyDomain.net/ticket/ ProxyPassReverse /ticket/ wss://ESXiServer.MyDomain.net/ticket/
and restart Apache:
sudo service apache2 restart
