✅ 1. Install Docker (if not installed)
sudo apt update
sudo apt install -y docker.io
sudo systemctl enable --now docker
Code language: CSS (css)✅ 2. Start Wetty using Docker (recommended + stable)
This avoids all Node/gc-stats errors you faced earlier.
Run Wetty in container:
sudo docker run -d \
--name wetty \
-p 80:3000 \
wettyoss/wetty \
--ssh-host=127.0.0.1
What this means:
- Docker runs Wetty internally on port 3000
- EC2 instance listens on port 80
- No need for Node.js / npm on host
- No gc-stats errors
- Very stable
Run Wetty in container BUT access the HOST Machine
sudo docker run -d \
--name wetty \
-p 80:3000 \
wettyoss/wetty \
--force-ssh \
--ssh-host=172.31.47.185 \
--ssh-port=22 \
--ssh-user=ubuntu✅ 3. Access Wetty in your browser
Use either:
http://13.200.229.28/wetty
Code language: JavaScript (javascript)or
http://ec2-13-200-229-28.ap-south-1.compute.amazonaws.com/wetty
Code language: JavaScript (javascript)⚠️ Wetty does NOT load on / → You must add /wetty
✅ 4. Verify Container is Running
docker ps
Should show:
PORTS
0.0.0.0:80->3000/tcp
I’m a DevOps/SRE/DevSecOps/Cloud Expert passionate about sharing knowledge and experiences. I have worked at Cotocus. I share tech blog at DevOps School, travel stories at Holiday Landmark, stock market tips at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow , and SEO strategies at Wizbrand.
Do you want to learn Quantum Computing?
Please find my social handles as below;
Rajesh Kumar Personal Website
Rajesh Kumar at YOUTUBE
Rajesh Kumar at INSTAGRAM
Rajesh Kumar at X
Rajesh Kumar at FACEBOOK
Rajesh Kumar at LINKEDIN
Rajesh Kumar at WIZBRAND
Find Trusted Cardiac Hospitals
Compare heart hospitals by city and services — all in one place.
Explore Hospitals
This article offers a clean, practical walkthrough for using Wetty to expose SSH sessions through a browser—a great fit for cloud‑based setups like AWS EC2. It clearly lays out the prerequisites (installing Docker) and the container command (docker run ‑d ‑‑name wetty ‑p 80:3000 wettyoss/wetty ‑‑ssh‑host=127.0.0.1) that avoids tedious Node/npm‑based installs. Besides the “how”, the article also points out useful details such as mapping host and container ports, using /wetty as the path, and verifying the container is running. For DevOps teams or interns building remote access or management workflows in a secure way, this tutorial bridges setup to usage extremely well.