Environment Variables

Server Environment Variables

Environment Variable	Server Argument	Description	Default
`DATA_DIR`	`data-dir`	Set the directory where the data should be stored (could be relative)	`./data/`
`UPTIME_KUMA_HOST` or `HOST`	`host`	Host to bind to, could be an ip.	`::`
`UPTIME_KUMA_PORT` or `PORT`	`port`	Port to listen to	`3001`
`UPTIME_KUMA_SSL_KEY` or `SSL_KEY`	`ssl-key`	Path to SSL key
`UPTIME_KUMA_SSL_CERT` or `SSL_CERT`	`ssl-cert`	Path to SSL certificate
`UPTIME_KUMA_CLOUDFLARED_TOKEN`	`cloudflared-token`	Cloudflare Tunnel Token (Available in 1.14.0)
`UPTIME_KUMA_DISABLE_FRAME_SAMEORIGIN`	`disable-frame-sameorigin`	By default, Uptime Kuma is not allowed in iframe if the domain name is not the same as the parent. It protects your Uptime Kuma to be a phishing website. If you don't need this protection, you can set it to `true`	`false`
`NODE_EXTRA_CA_CERTS`		Add your self-signed ca certs. (e.g. /cert/path/CAcert.pem) Read more
`NODE_TLS_REJECT_UNAUTHORIZED`		Ignore all TLS errors	`0`
`NODE_OPTIONS`		Set it to `--insecure-http-parser`, if you encountered error `Invalid header value char` when your website using WAF

Environment Variable	Description	Default
`PUID`	User id to access the data storage	`1000`
`PGID`	Group id to access the data storage	`1000`

Environment variable	Description	Default
`NODE_ENV`	Set the NodeJS environment flag	production
`UPTIME_KUMA_LOG_RESPONSE_BODY_MONITOR_ID`	Monitor ID - If provided, it will output the monitor's response to your console
`UPTIME_KUMA_HIDE_LOG`	(1.15.0) Examples: debug_monitor,info_monitor,debug_cert,warn_monitor
`SQL_LOG`	Set `1` to enable