Help with Proxy?

[KushX]

Sorry if this is the wrong place to post it. But it's been a few days of trying and I'm at my wits end!
I get a: GET https://checkmate.domain.com/api/v1/auth/users/superadmin [HTTP/1.1 502 Bad Gateway 276ms] when attempting to register.
I assume this is the API isn't reachable.

My portainer stack and nginx config are posted below. Hoping for some direction please.

services:
client:
image: ghcr.io/bluewave-labs/checkmate-client:latest
restart: always
environment:
UPTIME_APP_API_BASE_URL: "https://checkmate.domain.com/api/v1"
UPTIME_APP_CLIENT_HOST: "https://checkmate.domain.com"
ports:
- "5005:80"
- "5443:443"
depends_on:
- server
server:
image: ghcr.io/bluewave-labs/checkmate-backend:latest
restart: always
ports:
- "52345:52345"
depends_on:
- mongodb
environment:
- DB_CONNECTION_STRING=mongodb://mongodb:27017/uptime_db
- CLIENT_HOST=https://checkmate.domain.com
- JWT_SECRET=a97be3d562d89df2cf611ccfbcd19814fd078252fe716698694f0bbd613fda34
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
mongodb:
image: ghcr.io/bluewave-labs/checkmate-mongo:latest
restart: always
volumes:
- ./mongo/data:/data/db
command: ["mongod", "--quiet", "--bind_ip_all"]
healthcheck:
test: ["CMD", "mongosh", "--eval", "db.adminCommand('ping')", "--quiet"]
interval: 5s
timeout: 30s
start_period: 0s
start_interval: 1s
retries: 30

---

My NGINX CONFIG:
server {
if ($host = checkmate.domain.com) {
return 301 https://$host$request_uri;
} # managed by Certbot
listen 80;
listen [::]:80;
server_name checkmate.domain.com;
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl;
listen [::]:443 ssl;
proxy_send_timeout 330s;
proxy_read_timeout 330s;
server_name checkmate.domain.com;
ssl_certificate /etc/letsencrypt/live/checkmate.domain.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/checkmate.domain.com/privkey.pem; # managed by Certbot

ssl_session_cache shared:WEBSSL:10m;

ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers on;
ssl_ciphers EECDH+AESGCM:EDH+AESGCM;
ssl_ecdh_curve secp384r1;
add_header X-Content-Type-Options nosniff;

location /api/v1/ {
    proxy_pass http://127.0.0.1:52345/;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

location / {
    proxy_pass http://127.0.0.1:5005/;
    proxy_http_version 1.1;

    proxy_set_header Host $host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header X-Forwarded-Host $host:$server_port;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

}

[nicholasliverett]

I also had an issue with this, almost exactly the same, I was using pangolin as a reverse proxy. You have the proxy_pass as 52345 and the ports for the server set as 52345, but the UPTIME_APP_API_BASE_URL: "https://checkmate.domain.com/api/v1" does not have 52345. That may be your issue, I was running into blocked:csp issues.

[rotoiti]

I am also trying to set up Pangolin. My UPTIME_APP_API_BASE_URL is http://192.168.0.2:52345/api/v1 (so local address). Checkmate works fine internally, but through Pangolin it fails at login with "Server Connection Error". Nothing in the logs. Pangolin is set up with port 52345. Any clues?

[nicholasliverett]

I have checkmate and pangolin running on the same vps, (kinda redundant, whatever) but I set my checkmate container to 52345:443 and the api_base_url was set to https://mydomain.com/api/v1 (so are the other 2 host urls). I set pangolin's ip for the local site resource to the docker container name. That seemed to get it working, I also had to set the docker compose network to pangolin to get them to interact. I think either pangolin is not being routed correctly, or more likely, checkmate is just ignoring the requests because they don't match the base url. Checkmate is a little finnicky, I'm used to just spinning up uptime kuma and it working relatively easily lol.

[rotoiti]

Thanks for your reply Nicholas. My use case is internal monitoring, some of the services I wanted to monitor are not exposed via Pangolin. I installed Uptime Kuma which, as you mentioned, worked out of the box with Pangolin.

[txwgnd]

I have the exact same problem. I want to run Checkmate behind Pangolin as my reverse proxy.
If i spin up Checkmate with Monolithic compose file template it actually works locally when only IP's are used but using domains for everything that are handled by a reverse proxy doesn't seem to work. Is this an architectural limitation???