What's the reason for returnning 403

1. The problem I’m having:

My website returns 403 error

2. Error messages and/or full log output:

Return 403

3. Caddy version:

v2.7.6 h1:w0NymbG2m9PcvKWsrXO6EEkY9Ru4FJK8uQbYcev1p3A=

4. How I installed and ran Caddy:

a. System environment:

Debian 12.4, 6.1.0-15-cloud-amd64

b. Command:

sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo tee /etc/apt/trusted.gpg.d/caddy-stable.asc
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo apt update -y
sudo apt install caddy -y

c. Service/unit/compose file:

systemctl start caddy

d. My complete Caddy config:

foo.com {
 tls domain@foo.com
 root * /home/proname/website

5. Links to relevant resources:

I uploaded a folder with index.html file via scp -r website proname@ip:~/, and visit the website via foo.com, it returns 403, and I checked ls -lh

drwxr-xr-x 3 proname proname 4.0K Feb  4 06:48 website

I moved this folder website to /usr/share/caddy and checked ls -lh

drwxr-xr-x 3 proname proname 4.0K Feb  4 06:53 website

And this time, it works after I change root * /home/proname/website to root * /usr/share/caddy/website in the Caddyfile.

Any help? Thanks.

When running as a systemd service, Caddy runs as the caddy user. That user doesn’t have permission to access anything in /home because the x permission is needed for that user on every directory that is parent of the target, and /home does not have x for world.

Move your files elsewhere, like /srv or /var/www to allow Caddy to access them.

I see, thank you so much!!!