Setting up Totara/Moodle behind a Reverse Proxy (IBM WebSEAL)

Setting up Totara/Moodle behind a Reverse Proxy (IBM WebSEAL)

Adin Coup -
回帖数:5

Hi all I am new to this so please excuse me if I haven't included everything necessary,

I know this is a moodle forum but as Totara is based on Moodle, I was hoping I might find an answer here.

I would like to know if anyone else has previously set up Totara/Moodle, but running it behind a Reverse Proxy?


We have set up Totara 2.7.1 behind our Reverse Proxy server (IBM WebSEAL v6.1.1) which sits in our DMZ network, but the Totara web pages do not display correctly - i.e. images in the Navigation menu are not displaying, and the "Site Administration" menu link does not work when users click on it. It would seem that the Reverse Proxy might be having troubles with the CSS / Javascript / AJAX, but still unsure at this stage.


Will be logging a support call with IBM, but would like to hear if anyone else has had similar experiences with Reverse Proxy -> Totara?

Thanks for your help

回复Adin Coup

Re: Setting up Totara/Moodle behind a Reverse Proxy (IBM WebSEAL)

john Simpson -

Interesting. I didn't believe it until I searched. Totara is moodle 2.5.

Totara LMS is an open source distribution[1] of Moodle developed for the corporate and government market. \

http://en.wikipedia.org/wiki/Totara_LMS

So why not simply use moodle? Why two moodles? with one of them dated.

回复john Simpson

Re: Setting up Totara/Moodle behind a Reverse Proxy (IBM WebSEAL)

Just H -

For the business logic side of things. Have a look at ELIS too (similar to Totara but much more open), or Iomad.

回复john Simpson

Re: Setting up Totara/Moodle behind a Reverse Proxy (IBM WebSEAL)

Simon Coggins -

Hi John,

I'm afraid it was the wikipedia article that was a bit dated (I've updated it now), Totara's based on 2.7 currently.

Simon

回复Adin Coup

Re: Setting up Totara/Moodle behind a Reverse Proxy (IBM WebSEAL)

Simon Coggins -

Hi Adin,

I think your suspicions about it being an issue with the loading of external resources are likely to be right. There are a number of possible causes including a misconfigured webroot, SSL issues or possibly the proxy.

The first thing I would do would be to view the source of your homepage and check the path of resources like stylesheets or javascript are what you expect. If the path is correct I'd try manually loading one of those resources via a browser and seeing if you get any errors.

By the way, in this case I think your problem is unlikely to be Totara specific, but if you do want to ask any Totara specific questions you are welcome to self-register on our community site and post there.

Best of luck,

Simon