Grouped under the component believed to be causing them.
The certificate renewal unit is in a failed state. TLS certificates renew on a timer; if this stays failed, certificates will silently expire and every HTTPS site on this host will start refusing connections.
Run 'systemctl status certbot.service' and 'certbot renew --dry-run' to see why renewal is failing, and check certificate expiry with 'certbot certificates'.
nginx is configured to forward traffic to 127.0.0.1:3050, but no process on this host is bound to that port. Requests to ip10.ogmworld.com will return 502 Bad Gateway.
Start the service that is supposed to own port 3050, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.
nginx is configured to forward traffic to 127.0.0.1:3051, but no process on this host is bound to that port. Requests to investor.ogmworld.com will return 502 Bad Gateway.
Start the service that is supposed to own port 3051, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.
nginx is configured to forward traffic to 127.0.0.1:3060, but no process on this host is bound to that port. Requests to homechore.ogmworld.com will return 502 Bad Gateway.
Start the service that is supposed to own port 3060, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.
nginx is configured to forward traffic to 127.0.0.1:3070, but no process on this host is bound to that port. Requests to sentinelloop.ogmworld.com will return 502 Bad Gateway.
Start the service that is supposed to own port 3070, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.
nginx is configured to forward traffic to 127.0.0.1:7880, but no process on this host is bound to that port. Requests to meet.ogmworld.com will return 502 Bad Gateway.
Start the service that is supposed to own port 7880, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.
nginx is configured to forward traffic to 127.0.0.1:8090, but no process on this host is bound to that port. Requests to innovation.ogmworld.com, ip10.ogmworld.com will return 502 Bad Gateway.
Start the service that is supposed to own port 8090, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.
nginx is configured to forward traffic to 127.0.0.1:8091, but no process on this host is bound to that port. Requests to innovation.ogmworld.com will return 502 Bad Gateway.
Start the service that is supposed to own port 8091, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.
nginx is configured to forward traffic to 127.0.0.1:8092, but no process on this host is bound to that port. Requests to investor.ogmworld.com will return 502 Bad Gateway.
Start the service that is supposed to own port 8092, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.
Kubernetes API server is not serving on :6443. kubelet is running, and the static pod manifests are still in place, so this is a runtime failure rather than a removed cluster. kubectl reports: The connection to the server 31.220.52.144:6443 was refused - did you specify the right host or port?
Check the static pod containers with 'crictl ps -a | grep kube-apiserver' and read 'journalctl -u kubelet -p err -n 50' for the reason the container will not start. Until this is resolved, no deployment, scaling or self-healing can happen on this cluster.
nginx is configured to forward traffic to 127.0.0.1:32229, but no process on this host is bound to that port. Requests to stage.samskriti.ogmworld.com will return 502 Bad Gateway.
Start the service that is supposed to own port 32229, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.
chromadb, elasticsearch, mongodb, neo4j, nfs, postgresql, qdrant, redis are healthy on ogm-datacenter, but Stage — KVM2 cannot open a TCP connection to them (ports 6379, 6333, 2049, 9200, 8001, 5433, 27017, 7687). The services are up; the network path is not. Every expected datastore is blocked, which points at this host being absent from the datacenter firewall allow-list rather than at any individual service.
This is a network path problem, not a service problem. ogm-datacenter publishes these ports through Docker, which bypasses plain 'ufw allow' rules — the allow-list lives in the DOCKER-USER chain, maintained by scripts/setup-firewall.sh in the ogm-datacenter repository. Add this host's public IP to the ALLOWED_SOURCES array in that script and re-run it, then re-collect to confirm.
Running, but the container's own health check is failing.
The process is running but reporting itself unhealthy, so it is likely serving errors rather than being down outright. Check 'docker inspect --format "{{json .State.Health}}" ogm-console' for the failing probe output.
Container is exited.
Inspect why it stopped with 'docker logs --tail 100 ogm-dbgate'. If it is part of a compose project, 'docker compose up -d' from that project's directory will recreate it.
Container is exited.
Inspect why it stopped with 'docker logs --tail 100 ogm-uptime-kuma'. If it is part of a compose project, 'docker compose up -d' from that project's directory will recreate it.