Bug: <"Error: Endpoint is not available"> #1095

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

Originally created by @kbekus on 3/26/2024

Describe the bug
I'm just starting out with self hosting OneUptime and have followed the self hosting docker instructions. I've set up a reverse proxy using nginx proxy manager but when I connect to the instance and try to register a new account I get the error "Endpoint is not available".

image

To Reproduce
Steps to reproduce the behavior:

I've set up a new Debian 12 environment in an LXC on Proxmox. Installed the latest docker engine from the the docker repo. Pulled the git repo of OneUptime, edited the config.env and tried to run the service. All the individual containers come up fine. I've tried to launch the containers both using npm start and export $(grep -v '^#' config.env | xargs) && docker compose up --remove-orphans -d

Desktop (please complete the following information):

  • OS: Debian 12
  • Browser [e.g. chrome, safari]
  • Latest (7.0.1830)

Deployment Type
Self hosted docker

Additional context
I've tried both Chrome and Edge as browsers. The reverse proxy is handling SSL but onforwarding http only to OneUptime. I've tried HTTP_PROTOCOL both as http and https with the same result. I'm not seeing any useful errors in the logs.

*Originally created by @kbekus on 3/26/2024* **Describe the bug** I'm just starting out with self hosting OneUptime and have followed the self hosting docker instructions. I've set up a reverse proxy using nginx proxy manager but when I connect to the instance and try to register a new account I get the error "Endpoint is not available". ![image](https://github.com/OneUptime/oneuptime/assets/99165155/88d81521-7390-495c-94a9-faf7c4c5ced1) **To Reproduce** Steps to reproduce the behavior: I've set up a new Debian 12 environment in an LXC on Proxmox. Installed the latest docker engine from the the docker repo. Pulled the git repo of OneUptime, edited the config.env and tried to run the service. All the individual containers come up fine. I've tried to launch the containers both using npm start and export $(grep -v '^#' config.env | xargs) && docker compose up --remove-orphans -d **Desktop (please complete the following information):** - OS: Debian 12 - Browser [e.g. chrome, safari] - Latest (7.0.1830) **Deployment Type** Self hosted docker **Additional context** I've tried both Chrome and Edge as browsers. The reverse proxy is handling SSL but onforwarding http only to OneUptime. I've tried HTTP_PROTOCOL both as http and https with the same result. I'm not seeing any useful errors in the logs.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#1095