Ok, have done some 'leg work' for you ... ie, investigation, which may NOT be correct, but it might give you a clue as to what you need to do and what you need to ask hosting provider.
https://www.pair.com/support/knowledge_base/the_basics/troubleshooting_access_problems.html
on the page above it says under troubleshooting:
"There is a symbolic link called "public_html" in your home directory,
which can be used to reach your Web directory. You may also reach your
Web directory at the path "/usr/www/users/username/".
The directory for the moodle code needs to be inside public_html (normally). It is ... as anyone can see an elearning directory there and when accessing it one sees that Moodle is being served out.
But, one can also see a /usr/www/users/[yourusername]/mdata/moodledata/ directory in public_html. Moodle should object to that and it could be the source of your errors.
You need to ask your provider IF they could change the directory to be served out to be public_html/elearning/ That becomes your document root ... thus one would only need http://yoursite/ to access it. The moodledata folder now is the issue ... having apache access it securely.
IF the provider would allow you to have public_html still readable/accessible by apache then what you have in /usr/www/users/[yourusername]/public_html/mdata/moodledata could be moved to /usr/www/users/[yourusername]/public_html/moodledata/ and Moodle code (apache user/group) could still see the data folder. BUT no one could browse to http://yoursite/moodledata.
You would have to adjust your config.php files path to
/usr/www/users/[yourusername]/public_html/moodledata/
You could try this to see if the errors go away or not:
In the path to moodledata:
/usr/www/users/[yourusername]/mdata/moodledata/
Now it might work, but you'd need a way to prevent directory browsing ... ie, test to see if
you could access directly via URL line of a browser:
http://yoursite/mdata/
Without those secure changes, afraid Moodle might only half function and you'll continue to get 403 forbidden errors as Moodle code does NEED to be able to write to directories/files that are in moodledata.
When you talk to provider, might also give them this link:
https://docs.moodle.org/29/en/Installing_Moodle#Create_the_.28moodledata.29_data_directory
which explains.
'spirit of sharing', Ken
