"reverseproxy.statusError (reverseproxy.go:1269

Help
1

1. The problem I’m having:

I am having issue connecting my website due to reverse proxy issue.

2. Error messages and/or full log output:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

3. Caddy version:

v2.8.4 h1:q3pe0wpBj1OcHFZ3n/1nl4V4bxBrYoSoab7rL9BMYNk=

4. How I installed and ran Caddy:

sudo apt install -y certbot

chmod 750 /etc/letsencrypt/live/
chmod 750 /etc/letsencrypt/archive/
chmod 640 /etc/letsencrypt/archive/rnode01.canucks.icu/privkey1.pem
chgrp -R caddy /etc/letsencrypt/archive/
chgrp -R caddy /etc/letsencrypt/live/

sudo cat >/etc/caddy/Caddyfile <<EOL
{
https_port 443
on_demand_tls {
interval 60s
burst 5
}
}
rnode01.canucks.icu:443 {
reverse_proxy http://127.0.0.1:4020 {
# Forward Host header to the backend
header_up Host {host}
}
}
EOL

CMD ["/usr/bin/caddy", "run", "--config", "/etc/caddy/Caddyfile"]

a. System environment:

Ubuntu 24.04.1 LTS

b. Command:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

c. Service/unit/compose file:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

d. My complete Caddy config:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

5. Links to relevant resources:

2

Not sure why I didnt add logs but here : ● caddy.service - Caddy
Loaded: loaded (/usr/lib/systemd/system/caddy.service; enabled; preset: enabled)
Active: active (running) since Tue 2024-09-24 19:05:52 CEST; 26s ago
Docs: Welcome — Caddy Documentation
Main PID: 4235 (caddy)
Tasks: 12 (limit: 76964)
Memory: 12.0M (peak: 12.9M)
CPU: 66ms
CGroup: /system.slice/caddy.service
└─4235 /usr/bin/caddy run --environ --config /etc/caddy/Caddyfile

Sep 24 19:05:52 frhb81859ds caddy[4235]: {“level”:“info”,“ts”:1727197552.1765106,“logger”:“tls”,“msg”:“storage cleaning happened too recently; skipping for now”,“storage”:“FileStorage:/var/lib/caddy/.local/share/caddy”,“instance”:"0206e>
Sep 24 19:05:52 frhb81859ds caddy[4235]: {“level”:“info”,“ts”:1727197552.1765602,“logger”:“tls”,“msg”:“finished cleaning storage units”}
Sep 24 19:06:03 frhb81859ds caddy[4235]: {“level”:“error”,“ts”:1727197563.9911563,“logger”:“http.log.error”,“msg”:“dial tcp 127.0.0.1:4020: connect: connection refused”,“request”:{“remote_ip”:“2607:fea8:a5a:6580:2591:c625:8ca0:e85c”,"re>
Sep 24 19:06:05 frhb81859ds caddy[4235]: {“level”:“error”,“ts”:1727197565.2605994,“logger”:“http.log.error”,“msg”:“dial tcp 127.0.0.1:4020: connect: connection refused”,“request”:{“remote_ip”:“46.255.204.193”,“remote_port”:“32826”,"clie>
Sep 24 19:06:05 frhb81859ds caddy[4235]: {“level”:“error”,“ts”:1727197565.6114075,“logger”:“http.log.error”,“msg”:“dial tcp 127.0.0.1:4020: connect: connection refused”,“request”:{“remote_ip”:“46.255.204.193”,“remote_port”:“32826”,"clie>
Sep 24 19:06:05 frhb81859ds caddy[4235]: {“level”:“error”,“ts”:1727197565.6167316,“logger”:“http.log.error”,“msg”:“dial tcp 127.0.0.1:4020: connect: connection refused”,“request”:{“remote_ip”:“46.255.204.193”,“remote_port”:“32826”,"clie>
Sep 24 19:06:05 frhb81859ds caddy[4235]: {“level”:“error”,“ts”:1727197565.920443,“logger”:“http.log.error”,“msg”:“dial tcp 127.0.0.1:4020: connect: connection refused”,“request”:{“remote_ip”:“2607:fea8:a5a:6580:2591:c625:8ca0:e85c”,"rem>
Sep 24 19:06:06 frhb81859ds caddy[4235]: {“level”:“error”,“ts”:1727197566.6181529,“logger”:“http.log.error”,“msg”:“dial tcp 127.0.0.1:4020: connect: connection refused”,“request”:{“remote_ip”:“2607:fea8:a5a:6580:2591:c625:8ca0:e85c”,"re>
Sep 24 19:06:07 frhb81859ds caddy[4235]: {“level”:“error”,“ts”:1727197567.0722024,“logger”:“http.log.error”,“msg”:“dial tcp 127.0.0.1:4020: connect: connection refused”,“request”:{“remote_ip”:“2607:fea8:a5a:6580:2591:c625:8ca0:e85c”,"re>
Sep 24 19:06:12 frhb81859ds caddy[4235]: {“level”:“error”,“ts”:1727197572.5774076,“logger”:“http.log.error”,“msg”:“dial tcp 127.0.0.1:4020: connect: connection refused”,“request”:{“remote_ip”:“51.195.47.67”,“remote_port”:“52118”,"clien

3

Is your upstream running? Seems down

2 Likes
4

Please fill out every part of the help topic template, as per the forum rules. Please mind your post’s formatting, it’s a mess. Config and logs should go in code blocks (the </> button, or the ``` parts you see in the template).

3 Likes
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.