Apache as a reverse proxy

[ap0int3d]

Hi

Since Apache is not in the documentation, here is the Apache config for WebSSH I use in my lab (it is based on the nginx configuration provided in the documentation). Nothing fancy but hopefully it can help someone.

Below is the configuration for TLS support and redirection from HTTP to HTTPS.
These settings require mod_headers, mod_proxy, mod_proxy_http and mod_ssl.

<VirtualHost *:80>
    ServerName webssh.yourdomain.com
    Redirect permanent / https://webssh.yourdomain.com/
</VirtualHost>

<VirtualHost *:443>
    ServerName webssh.yourdomain.com

    SSLEngine on
    SSLCertificateFile /path/to/cert.pem
    SSLCertificateKeyFile /path/to/private_key.pem
    SSLCACertificateFile /path/to/ca_certificates.pem

    ProxyPreserveHost On
    ProxyRequests Off

    ProxyPass / http://localhost:5000/
    ProxyPassReverse / http://localhost:5000/

    RequestHeader set Upgrade "websocket"
    RequestHeader set Connection "Upgrade"
    RequestHeader set Host %{HTTP_HOST}s
    RequestHeader set X-Real-IP %{REMOTE_ADDR}s
    RequestHeader set X-Forwarded-For "%{REMOTE_ADDR}s"
    RequestHeader set X-Forwarded-Proto "%{REQUEST_SCHEME}s"
</VirtualHost>

[bifrost0x]

Thanks for sharing this configuration. I used the discussion to extend the deployment documentation in PR #122:

• added a proxy-neutral contract that also applies to Traefik, Nginx, Caddy, Apache, and other reverse proxies;
• added Apache httpd 2.4.47+ examples for both root and /webssh subfolder deployments;
• documented WebSocket forwarding through mod_proxy_http, trusted proxy counts, forwarded headers, secure origins/cookies, and private backend networking;
• aligned the Nginx examples with the documented X-Forwarded-Host behavior;
• noted the separate mod_proxy_wstunnel requirement for older Apache releases.

The application remains proxy-agnostic; the PR adds validated deployment guidance without introducing Apache-specific backend logic.

PR: #122