Yes the boilerplate virtualmin index.html is in the public_html folder. Changing the folder and file permissions fixes the issue, however I’m trying to avoid having to modify the permissions every time I create a new virtual server.
I’m still blocked on this…can’t figure out where the issue lies. Every new virtual host is created with 750 permissions, and all visits to url’s in that new virtual host result in a 403 (navigating to an existing file).
If I manually modify to 755, everything works from there on out.
Can anybody guide me on how to change the default permission for apache virtual host folders, without having to explicitly set the permission in the template and thus having to create a custom set of apache directives?
I’m actually not understanding why 750 does not work as well – by running under the user account and group, shouldn’t 750 allow access to html files?
I had a similar problem with one migrated domain a couple of weeks ago, but didn’t bother troubleshooting it because it was a small static site and there were no databases and no important mail to worry about. I just re-created it and re-uploaded it.
No, not migrated. This is brand new Google Cloud Centos 8 instance, immediate Virtualmin installation, and then this persistent permissions problem with virtual hosts. I have a long running Centos 7 installation working well, and I’m not sure what is different here?
Perhaps some more eyes can take a look here? I could really use some help and can’t find anything in the forum related to Centos 8 and folder permissions.