Once your new Ethora server or an updated version is deployed, it is always a good idea to run additional Quality Assurance procedures to make sure everything works as intended. Here are some recommendations:
Smoke (5–10 min)
“is the stack up and routing correctly?”
Run deploy/scripts/qa-check.sh and deploy/scripts/health-check.sh (they already cover API ping, Swagger JSON validity, MinIO health, XMPP websocket probe, etc.).
Manually open:
API health: https://api.<your-domain>.com/ping (or /v1/ping)
Swagger: https://api.<your-domain>.com/api-docs/ and https://api.<your-domain>.com/api-docs/swagger.json
Frontend: your web app loads, login works, no 50x loops
Core functional flows (15–30 min)
“what a real user does”
Create/login a user
Join/create a room
Send/receive messages (two users / two browsers)
Attach/upload a file (if enabled)
Presence/room membership changes (invite/remove)
Logout/login again (session refresh)
Automated end-to-end regression (best ongoing signal):
Use Uptime “journey_advanced” as your repeatable regression gate (chat membership + XMPP delivery + file upload checks).