Visvanath Ratnaweera

Copy some simple HTML file to the moodle directory (where you have config.php) and try to access it in the browser, the URL should be something like http://yourcurrentmoodle/test.html. The content of the HTML should be displayed. If not, the problem is with the web server (not Moodle).

Once that problem is solved, the index.php in the Moodle source will answer the request to Moodle.

The method has remained the same since the early days. See for example https://docs.moodle.org/19/en/Site_restore from Nov 2010!

Hi

The steps are simple, see https://docs.moodle.org/33/en/Site_restore. Your problem will be how to handle those monster data!

Hi

OK, you switch the VM between production and test without touching it, just with DNS changes. This is a tough one then.

But if you can't reproduce, there is no way of confirming an idea. My input was in my previous post: a) never seen Moodle or Debian/Ubuntu Linux doing this b) the complaint comes from a lower level, the VMWare hint I found sounds closer.

Did you see this https://stackoverflow.com/questions/13862908/ssl-certificate-is-not-trusted-on-mobile-only ?

Source: https://moodle.org/mod/forum/discuss.php?d=326457#p1313013