Hello Bitnami Experts,
I'd previously posted this issue in the open edx operations forum before isolating it as a bitnami-specific problem.
System: AWS t2.medium
Image: Bitnami Ficus v3.2 on Ubuntu 14.04.3 (one-click install)
Theme: Custom, None (occurs in both configs)
Modifications: Many, None (occurs in both configs)
Conf: Occurs with no config to many configured items
I've noted the same error on 4 separate images of Ficus v3.2
Problem: When the root LMS page loads in a browser, everything displays as expected. If a user refreshes the browser page, or logs-in to view the course list, the preview image tiles for the courses do not appear (shows a broken link instead). Browser reports the problem as a 403 forbidden error when trying to load the image resource. Waiting approximately 5 minutes and refreshing the page will allow the images to be loaded/viewed again, but another refresh breaks the links. Looking at the source displayed in the browser, I can see that the links to the images that are sent from the server actually change. Here is what the image markup and screenshots for the edX demonstration course tile looks like:
After refresh/broken link:
**THIS ERROR OCCURS IMMEDIATELY FOLLOWING ANY ACT TO DISABLE THE BITNAMI BANNER!!!
More specifically, I've used the command:
sudo /opt/bitnami/apps/edx/bnconfig --disable_banner 1
AND I've manually disabled it by commenting out the Include banner line in the httpd-lms.conf
Both have the same result of removing the banner, but also causing resource instability with the course images. Also odd is that the error is persistent. In the second case, when I remove the comment and reinstate the banner via the second method, I get the banner back but still have the resource instabilities.
You'll notice that characters are being replaced or substituted in the image src. Any ideas why this is happening? My initial guess is that Apache was the culprit, but I've done nothing to alter Apache's configuration files with the exception of the banner. Also, I find the behavior vexing in that it occurs in the initial load, and then resets (perhaps when a very short session variable expires). The behavior is odd, but predictable.
I've found nothing in the edx log files (even set to debug mode) to indicate what is happening. Here is the relevant section of the apache error log showing the 403 errors:
[Mon Aug 07 10:43:00.713440 2017] [authz_core:error] [pid 3244] [client 184.108.40.206:49904] AH01630: client denied by server configuration: uri /xasset-v1,3AedX+DemoX+Demo_Course+type,40asset+block,40images_course_image.jpg.pagespeed.ic.d9usl8eeeb.webp, referer: http://x.org/
[Mon Aug 07 10:43:00.733161 2017] [authz_core:error] [pid 3244] [client 220.127.116.11:49904] AH01630: client denied by server configuration: uri /xasset-v1,3Ax+WF001+2017+type,40asset+block,40orville-wilbur-color.jpg.pagespeed.ic.z_SJrsufvu.webp, referer: http://x.org/
[Mon Aug 07 10:43:00.756836 2017] [authz_core:error] [pid 3244] [client 18.104.22.168:49904] AH01630: client denied by server configuration: uri /xasset-v1,3Ax+WF002+2017+type,40asset+block,40plotting.jpg.pagespeed.ic.PX8gA7ImBp.webp, referer: http://x.org/
[Mon Aug 07 10:43:00.776814 2017] [authz_core:error] [pid 3244] [client 22.214.171.124:49904] AH01630: client denied by server configuration: uri /xasset-v1,3Ax+WF003+2017+type,40asset+block,40ang_f16.png.pagespeed.ic.EGMqsm-Ieo.webp, referer: http://x.org/
I've tried to view the page from multiple browser types and different IP addresses - same result, so the error appears to be with the server throwing junk into the asset address.
I'm still troubleshooting this issue and will post anything that I find, but I figured it is bigger than myself since I've experienced it with various configurations on multiple images. Any help the community can provide would be much appreciated.