by Jake Dallimore.
Given the complexity of the setup, unless there's a crystal clear description, and steps to reproduce it, issue like this can be hard to reproduce and it becomes less likely someone will work on it, were a tracker issue to be created (and may just sit there in jira for some time unfortunately). Can a reverse proxy nginx container be used instead to trigger the same problem? That would assist in reproduction of the problem. Can you see the requests hitting the Moodle site? You're of course welcome to create an issue on tracker.moodle.org, but without all the information we can get, it becomes very hard to reproduce and runs the risk of being closed.
I will add that that file (mod/lti/certs.php) is a public file so should always be accessible. I.e. the tool should be able to read it any time. Can you access the file directly? You say it's fails with no errors, but what about the HTTP trace?
Hope that helps and sorry I can't be of more help,
Jake
I will add that that file (mod/lti/certs.php) is a public file so should always be accessible. I.e. the tool should be able to read it any time. Can you access the file directly? You say it's fails with no errors, but what about the HTTP trace?
Hope that helps and sorry I can't be of more help,
Jake