How eddy165/private-web-access-ssh works
This repository demonstrates private web access through an SSH local port forward. The principal flow is browser → client-side forwarded port → encrypted SSH connection → server-side loopback web service. The Python service serves a static page and status/health endpoints; documented PowerShell utilities support starting and checking the server and tunnel. Tunnel behavior and the utilities are described in the README, but their source was not sampled, so those links rely on that documentation rather than inspected implementations.
Main entry points: server.py Python HTTP server · start_tunnel.ps1 Tunnel startup · start_private_server.ps1 Server startup · check_server.ps1 Server checks
Components 12
Client access
- Local forward :8080
SSH transport
- OpenSSH client
- OpenSSH server
- Tunnel startup
private-web-access-ssh/scripts/start_tunnel.ps1
Private web service
- Python HTTP server
private-web-access-ssh/private_web/server.py - Static web page
private-web-access-ssh/private_web/static/index.html - Status endpoint
private-web-access-ssh/private_web/server.py - Health endpoint
private-web-access-ssh/private_web/server.py - Server startup
private-web-access-ssh/scripts/start_private_server.ps1
Connectivity tools
- Server checks
private-web-access-ssh/scripts/check_server.ps1 - Tunnel checks
private-web-access-ssh/scripts/check_tunnel.ps1
Other components
- Web browser
Connections 9
- Web browser → Local forward :8080: requests via
README.md - Local forward :8080 → OpenSSH client: forwards through
README.md - OpenSSH client → OpenSSH server: connects encrypted
README.md - OpenSSH server → Python HTTP server: forwards to loopback
README.md - Python HTTP server → Static web page: serves
private-web-access-ssh/private_web/server.py - Server startup → Python HTTP server: starts
README.md - Tunnel startup → OpenSSH client: starts
README.md - Server checks → Python HTTP server: checks
README.md - Tunnel checks → OpenSSH client: checks
README.md