Forum Problems Installing LAMS: Re: author module and localhost


 
Search: 

2: Re: author module and localhost
In response to 1 06/15/08 04:57 AM
[ Reply | Forward ]
Hi Manolis,

It's common for non-80 web ports not to be open in firewalls. It's also nice to have webapps available on port 80 so you don't have to type the port in your browser. For both these reasons there are a few solutions to make a tomcat app like lams available on port 80, using proxy pass on apache is one of them - I like to use mod_jk myself...

Loading author involves a few javascript and flash calls back to the lams server - for this it uses the ServerURL value in the lams sysadmin configuration. If the URL in your browser and the ServerURL domains don't match, then javascript (or is it flash? or both?) won't complete its work and author won't load. It's not a configuration or network issue, just a security measure of javascript/flash. Quick fix is to simply access LAMS via the URL used in your value for ServerURL. Longer term, just put the URL you want your server to be known by as your value for ServerURL in the lams sysadmin interface.

Hope some of this is helpful!

ps changing lams.properties won't have an effect, it's a kind of caveat that we only use this file at installer/updater time, not run time...

Posted by Jun-Dir Liew

Reply to first post on this page
Back to Problems Installing LAMS