No description
  • JavaScript 74.7%
  • CSS 25%
  • HTML 0.3%
Find a file
2026-02-19 20:25:43 +00:00
backend Fix issue where Express 5 Requires named wildcare parms 2026-02-19 20:25:43 +00:00
frontend Delete frontend/package-lock.json 2026-02-19 12:29:51 -05:00
.gitignore Update .gitignore 2026-02-19 12:30:16 -05:00
LICENSE Initial commit 2026-02-19 11:45:31 -05:00
package.json Serve frontend from backend in production, update scripts and README 2026-02-19 20:20:27 +00:00
README.md Update README.md 2026-02-19 15:23:19 -05:00

Cyphyrix Status Page

A self-hosted, real-time status page for monitoring your services, APIs, and infrastructure.

MIT License Node.js 24 LTS SQLite


Cyphyrix Status Page

A free and open source status page you can self-host to monitor uptime, track incidents, and show your users a clean, real-time view of your services. No external database required, everything runs on SQLite.

Features

Real-time monitoring — monitor HTTP/HTTPS endpoints, TCP ports, and ping availability with customisable check intervals from 10 seconds to 1 hour.

Live status updates — WebSocket-powered real-time updates pushed to the public status page and admin dashboard as checks complete.

Admin dashboard — add, edit and remove endpoints, manage incidents, configure site settings, and manage users from a single panel.

Public status page — a clean, responsive page showing current status, response times, active incidents, and overall system health.

Incident management — create, update, and resolve incidents with severity levels and link them to affected endpoints.

Uptime tracking — automatic uptime percentage calculation over configurable time periods.

Role-based access — admin and viewer roles with enforced permissions on all protected routes.

Zero external dependencies — SQLite database, no Redis or Postgres required. Just Node.js.

Note

This project is actively developed. Email/Slack/Discord notifications, detailed analytics, custom branding, and SLA reporting are planned for future releases.

Requirements

  • Node.js 24 LTS or newer
  • A Linux, macOS, or Windows machine

Quick Start

1. Clone and install

git clone https://git.cyphyrix.xyz/Rinanyae/Cyphyrix_Status or download a release.
cd status-page

# Install all dependencies (root, backend, and frontend)
npm run install-all

2. Configure

cp backend/.env.example backend/.env

Edit backend/.env and change the JWT secret to a strong random value:

PORT=5000
NODE_ENV=production
JWT_SECRET=replace_with_a_strong_random_string
DATABASE_PATH=../data/status.db
FRONTEND_URL=https://status.example.com

Important

Never deploy with the default JWT secret. Generate one with openssl rand -hex 64 or similar.

3. Run

Development (runs React dev server + backend with hot reload):

npm run dev

Production (builds frontend, serves everything from the backend):

# Build the frontend
npm run build

# Start the server
npm start

Everything runs on a single port in production:

URL
Status page http://localhost:5000
Admin panel http://localhost:5000/admin
API http://localhost:5000/api

On first launch you'll be guided through a setup wizard to create your admin account and configure site settings.

Production Deployment

Running with PM2

# Install PM2 globally
npm install -g pm2

# Build the frontend first
npm run build

# Start the app
pm2 start "npm start" --name cyphyrix-status

# Auto-start on reboot
pm2 startup
pm2 save

# View logs
pm2 logs cyphyrix-status

Using a Reverse Proxy (Nginx)

Since everything runs on port 5000 in production, the Nginx config is straightforward:

server {
    listen 80;
    server_name status.example.com;

    location / {
        proxy_pass http://localhost:5000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_cache_bypass $http_upgrade;
        proxy_buffering off;
    }
}

Tip

Use Certbot to add HTTPS with a free Let's Encrypt certificate. Update FRONTEND_URL in your .env to match your domain.

Troubleshooting

Port already in use
lsof -i :5000
lsof -i :3000
kill -9 <PID>
Database issues

Delete the database to reset (this loses all data):

rm data/status.db
npm start

The database will be recreated automatically on startup.

WebSocket not connecting

Make sure FRONTEND_URL in backend/.env matches your actual frontend URL. If using a reverse proxy, ensure the /socket.io path is proxied correctly.

License

MIT


Made with care for anyone who needs a simple, self-hosted status page.

Made with care for anyone who needs a simple, self-hosted status page.