You are not logged in.
This problem came about a few days after apache 2.4.65-3 was installed
and carried on into 2.4.65-4 .
There are a number of pages and "apps" associated with this web server. They all work.
However, one page will not come up and issues a 403 error with:
" It is either read-protected or not readable by the server."
Basically this page has a directory "link" in the /srv/http directory where all the
other pages are served from. It is unique in that it is the only "linked" directory
and points to a directory of files on a RAID. This has worked reliably for over
8 years. All directories are "rwxr_xr_x" and all files are at least "rw_r__r__" .
The problem started after a pacman update a few days after 2.4.65-3 went into
production, and persisted after an update a few hours later to 2.4.65-4. While this
is specific to this one web page, there appears to be no issues following this link to
manipulating these files by any other app I tried so far. So it is an apache problem,
apparently not caused by apache...
Any ideas on solving this?
Last edited by W54J04S07T (2025-09-21 19:02:18)
Offline
Offline
Awesome how you picked that one out!
For the record, the last entry as follows worked:
# systemctl edit httpd
insert ...
[Service]
ProtectHome=read-only
write out
and
#systemctl restart httpd
FYI and Thank You
Offline