Homelab

371 readers

9 users here now

Rules

Be Civil.
Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
No memes or potato images.
We love detailed homelab builds, especially network diagrams!
Report any posts that you feel should be brought to our attention.
Please no shitposting or blogspam.
No Referral Linking.
Keep piracy discussion off of this community

founded 11 months ago

MODERATORS

[email protected]

How to configure Uptime Kuma behind an Nginx reverse proxy? (alien.top)

submitted 9 months ago by [email protected] to c/[email protected]

1 comments fedilink hide all child comments

I just installed Uptime Kuma in a Docker container on the same host and custom bridge network as my NPM container. I can reach it if I navigate directly to host ip:port, but not if I go through the reverse proxy. I saw the note about special configuration in order to reach it behind a reverse proxy, but I don't think I'm doing it correctly.

I added the following configuration to the Advanced tab of the Uptime Kuma proxy host. uptimekuma.mydomain.com exists in my local DNS and points to my NPM, just like everything else that I have pointing at it. Any ideas what I'm doing wrong?

server {

listen 80;

server_name uptimekuma.``mydomain``.com``;

location / {

proxy_pass http://localhost:3001;

proxy_http_version 1.1;

proxy_set_header Upgrade $http_upgrade;

proxy_set_header Connection "upgrade";

proxy_set_header Host $host;

}

top 1 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 9 months ago

The formatting didn't come through correctly in my post, but I have it formatted exactly per the instructions on this page. The only change I made was the server_name field