Bug:Unable to start self-hosted docker OneUpTime #889

Closed
opened 2026-04-05 16:23:28 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @AJorge95 on 6/20/2024

Greetings,

I have followed all the instructions, but my OneUpTime instance is unable to boot correctly.

From the logs below, you can see that the server is booting. However, when I open the page in a web browser, it always returns "Oops, something went wrong."

image

or

image

> @oneuptime/root@3.0.2 start /home/ajorge/oneuptime

export $(grep -v '^#' config.env | xargs) && docker compose up --remove-orphans -d $npm_config_services && npm run status-check

[+] Running 18/18
✔ Container oneuptime-e2e-1 Removed 0.0s
✔ Container oneuptime-test-server-1 Removed 0.0s
✔ Container oneuptime-fluentd-1 Removed 0.0s
✔ Container oneuptime-redis-1 Started 2.7s
✔ Container oneuptime-clickhouse-1 Started 3.0s
✔ Container oneuptime-ingress-1 Started 3.0s
✔ Container oneuptime-admin-dashboard-1 Started 2.6s
✔ Container oneuptime-otel-collector-1 Started 3.0s
✔ Container oneuptime-isolated-vm-1 Started 3.0s
✔ Container oneuptime-ingestor-1 Started 2.6s
✔ Container oneuptime-status-page-1 Started 2.6s
✔ Container oneuptime-probe-2-1 Started 2.6s
✔ Container oneuptime-accounts-1 Started 2.8s
✔ Container oneuptime-app-1 Started 3.0s
✔ Container oneuptime-dashboard-1 Started 3.0s
✔ Container oneuptime-probe-1-1 Started 2.7s
✔ Container oneuptime-postgres-1 Started 2.3s
✔ Container oneuptime-haraka-1 Started 2.3s

@oneuptime/root@3.0.2 status-check /home/ajorge/oneuptime
bash ./Tests/Scripts/status-check.sh $npm_config_services

We will need to wait ~5-10 minutes for things to settle down, migrations to finish, and TLS certs to be issued.

⏳ Waiting for OneUptime to boot (this will take a few minutes)

App localhost returned HTTP 502, retrying in 15 seconds. Usually takes a few minutes to boot.
App localhost returned HTTP 502, retrying in 15 seconds. Usually takes a few minutes to boot.
App localhost returned HTTP 502, retrying in 15 seconds. Usually takes a few minutes to boot.
App localhost returned HTTP 502, retrying in 15 seconds. Usually takes a few minutes to boot.
✅ App endpoint is up (localhost)
✅ App (Status Check) endpoint is up (localhost/status)
✅ App (Ready Check) endpoint is up (localhost/status/ready)
Dashboard localhost/dashboard returned HTTP 301, retrying in 15 seconds. Usually takes a few minutes to boot.

Configuration File:

# Please change this to the domain of the server where OneUptime is hosted.
HOST=192.168.1.102

# If this server is hosted on SSL/TLS then change this to https
HTTP_PROTOCOL=http

# Secrets - PLEASE CHANGE THESE. Please change these to something random. All of these can be different values.
ONEUPTIME_SECRET=please-change-this-to-random-value
DATABASE_PASSWORD=please-change-this-to-random-value
CLICKHOUSE_PASSWORD=please-change-this-to-random-value
REDIS_PASSWORD=please-change-this-to-random-value
ENCRYPTION_SECRET=please-change-this-to-random-value
GLOBAL_PROBE_1_KEY=please-change-this-to-random-value
GLOBAL_PROBE_2_KEY=please-change-this-to-random-value
INTERNAL_SMTP_PASSWORD=please-change-this-to-random-value

# Example values (these should be replaced with your own)
ONEUPTIME_SECRET=821f57e095e97915
DATABASE_PASSWORD=f046cd94b0327aa0
CLICKHOUSE_PASSWORD=a5686c5925a3d51d
REDIS_PASSWORD=a760573b17b807ce
ENCRYPTION_SECRET=a171fc67ef270192
GLOBAL_PROBE_1_KEY=cdd04392f06fef97
GLOBAL_PROBE_2_KEY=ca0b5434325b7144
INTERNAL_SMTP_PASSWORD=17077fe1909bb311

# OTEL HOST - if you want the collector to be hosted on a different server, change this to the IP of that server.
OTEL_COLLECTOR_HOST=

# FLUENTD_HOST - if you want Fluentd to be hosted on a different server, change this to the IP of that server.
FLUENTD_HOST=

# OneUptime Port. This is the port where OneUptime will be hosted.
ONEUPTIME_HTTP_PORT=80
ONEUPTIME_HTTPS_PORT=443

# To attach the status page to custom domains, use this setting.
# For example, if you want the status page to be hosted on status.yourcompany.com, then:
# 1. Create an A record in your DNS provider with the name "oneuptime.yourcompany.com" and value to the Public IP of the server OneUptime is deployed on.
# 2. Set the STATUS_PAGE_CNAME_RECORD to "oneuptime.yourcompany.com"
# 3. Create a CNAME record in your DNS provider with the name "status.yourcompany.com" and value "oneuptime.yourcompany.com"
STATUS_PAGE_CNAME_RECORD=oneuptime.yourcompany.com
*Originally created by @AJorge95 on 6/20/2024* Greetings, I have followed all the instructions, but my OneUpTime instance is unable to boot correctly. From the logs below, you can see that the server is booting. However, when I open the page in a web browser, it always returns "Oops, something went wrong." ![image](https://github.com/OneUptime/oneuptime/assets/16062031/8ea8e67f-2f1f-4e63-9824-ab05a7726438) or ![image](https://github.com/OneUptime/oneuptime/assets/16062031/38fb1a56-025e-4b8c-9621-ef19d1aad41f) ``` > @oneuptime/root@3.0.2 start /home/ajorge/oneuptime export $(grep -v '^#' config.env | xargs) && docker compose up --remove-orphans -d $npm_config_services && npm run status-check [+] Running 18/18 ✔ Container oneuptime-e2e-1 Removed 0.0s ✔ Container oneuptime-test-server-1 Removed 0.0s ✔ Container oneuptime-fluentd-1 Removed 0.0s ✔ Container oneuptime-redis-1 Started 2.7s ✔ Container oneuptime-clickhouse-1 Started 3.0s ✔ Container oneuptime-ingress-1 Started 3.0s ✔ Container oneuptime-admin-dashboard-1 Started 2.6s ✔ Container oneuptime-otel-collector-1 Started 3.0s ✔ Container oneuptime-isolated-vm-1 Started 3.0s ✔ Container oneuptime-ingestor-1 Started 2.6s ✔ Container oneuptime-status-page-1 Started 2.6s ✔ Container oneuptime-probe-2-1 Started 2.6s ✔ Container oneuptime-accounts-1 Started 2.8s ✔ Container oneuptime-app-1 Started 3.0s ✔ Container oneuptime-dashboard-1 Started 3.0s ✔ Container oneuptime-probe-1-1 Started 2.7s ✔ Container oneuptime-postgres-1 Started 2.3s ✔ Container oneuptime-haraka-1 Started 2.3s @oneuptime/root@3.0.2 status-check /home/ajorge/oneuptime bash ./Tests/Scripts/status-check.sh $npm_config_services We will need to wait ~5-10 minutes for things to settle down, migrations to finish, and TLS certs to be issued. ⏳ Waiting for OneUptime to boot (this will take a few minutes) App localhost returned HTTP 502, retrying in 15 seconds. Usually takes a few minutes to boot. App localhost returned HTTP 502, retrying in 15 seconds. Usually takes a few minutes to boot. App localhost returned HTTP 502, retrying in 15 seconds. Usually takes a few minutes to boot. App localhost returned HTTP 502, retrying in 15 seconds. Usually takes a few minutes to boot. ✅ App endpoint is up (localhost) ✅ App (Status Check) endpoint is up (localhost/status) ✅ App (Ready Check) endpoint is up (localhost/status/ready) Dashboard localhost/dashboard returned HTTP 301, retrying in 15 seconds. Usually takes a few minutes to boot. ``` Configuration File: ``` # Please change this to the domain of the server where OneUptime is hosted. HOST=192.168.1.102 # If this server is hosted on SSL/TLS then change this to https HTTP_PROTOCOL=http # Secrets - PLEASE CHANGE THESE. Please change these to something random. All of these can be different values. ONEUPTIME_SECRET=please-change-this-to-random-value DATABASE_PASSWORD=please-change-this-to-random-value CLICKHOUSE_PASSWORD=please-change-this-to-random-value REDIS_PASSWORD=please-change-this-to-random-value ENCRYPTION_SECRET=please-change-this-to-random-value GLOBAL_PROBE_1_KEY=please-change-this-to-random-value GLOBAL_PROBE_2_KEY=please-change-this-to-random-value INTERNAL_SMTP_PASSWORD=please-change-this-to-random-value # Example values (these should be replaced with your own) ONEUPTIME_SECRET=821f57e095e97915 DATABASE_PASSWORD=f046cd94b0327aa0 CLICKHOUSE_PASSWORD=a5686c5925a3d51d REDIS_PASSWORD=a760573b17b807ce ENCRYPTION_SECRET=a171fc67ef270192 GLOBAL_PROBE_1_KEY=cdd04392f06fef97 GLOBAL_PROBE_2_KEY=ca0b5434325b7144 INTERNAL_SMTP_PASSWORD=17077fe1909bb311 # OTEL HOST - if you want the collector to be hosted on a different server, change this to the IP of that server. OTEL_COLLECTOR_HOST= # FLUENTD_HOST - if you want Fluentd to be hosted on a different server, change this to the IP of that server. FLUENTD_HOST= # OneUptime Port. This is the port where OneUptime will be hosted. ONEUPTIME_HTTP_PORT=80 ONEUPTIME_HTTPS_PORT=443 # To attach the status page to custom domains, use this setting. # For example, if you want the status page to be hosted on status.yourcompany.com, then: # 1. Create an A record in your DNS provider with the name "oneuptime.yourcompany.com" and value to the Public IP of the server OneUptime is deployed on. # 2. Set the STATUS_PAGE_CNAME_RECORD to "oneuptime.yourcompany.com" # 3. Create a CNAME record in your DNS provider with the name "status.yourcompany.com" and value "oneuptime.yourcompany.com" STATUS_PAGE_CNAME_RECORD=oneuptime.yourcompany.com ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#889