Hi
Thanks for providing so much info!
The problem here seems to be (Linux) file permissions.
While you did set 0777
(u=rwx,g=rwx,o=rwx
) on the files you want to access, the caddy user still has to have execution access for every parent folder in the path to traverse/reach the file.
This is nothing caddy can change - this is just how Linux file permissions work.
Pick one:
- So you could either use a totally different folder like
/srv
or/var/www
(recommended)
- OR add execution perms for literally any user on the inhji home directory via
chmod a+x /home/inhji
chmod a+x /home/inhji/www
chmod a+x /home/inhji/www/mirage
chmod a+x /home/inhji/www/mirage/data
-
chmod a+x /home/inhji/www/mirage/data/uploads
and finally -
chmod -R a+x /home/inhji/www/mirage/data/uploads
to recursively go over all potential subdirs indata/uploads
.
I strongly advise against runningchmod -R a+x /home/inhji
because this will change EVERY SUBDIRECTORY in/home/inhji
- OR add exec perms only for a group caddy is part of and set on the folders via
chown
on the inhji home directory via the same sequence above but this time usingchmod g+x
instead ofo+x