witch (25th June 2009)
mpm_common - Apache HTTP Server
in the httpd.conf and restart apacheFor example, to make the server accept connections on both port 80 and port 8000, use:
witch (25th June 2009)
Sorry, I have no idea what any of that means...How do I get it to listen to port 8000 - what would the address bit be?
I am a hardware engineer at heart and I just don't really get what I am doing here! (what is this place?)
Oh, and will there be a problem with the new server being 2008?
Last edited by witch; 25th June 2009 at 01:44 PM.
the listen bit is a line in a file called httpd.conf. listen determines the port that the webserver listens on - ie http://servername:81 means that it's set to:Sorry, I have no idea what any of that means...what will the 'listen' bit do? I wouldn't want to break anything (again)
actually, it could beCode:listen 81
where x is ip addressCode:listen xxx.xxx.xxx.xxx:81
if you change it to 80 then you won't need to type in :81 - but there may have been another reason for this (if IIS is installed on the same server for example)
try it, if it breaks you have backed up the httpd.conf file - right
We only have one server so IIS is definitely installed on the same one - what do I do in this case?
No, I couldn't do that - it is definitely used here - we had to go into it to find the intranet page so that we could set up a link to Moodle.
So does that mean I can't move Moodle from Apache to IIS then? Still confused
Last edited by witch; 25th June 2009 at 02:08 PM.
To get Apache running...
Add another IP to the server
Then enter IIS, go into the properties panel, change from (All Unassigned) to the old IP.
Open the httpd.conf and change the line that reads
Replacing xxx.xxx.xxx.xxx with the new ip.
Restart IIS, (re)start Apache.
Goodness I am confused...
We already have IIS and Port 80 is taken by something or other (website?). So, we put the moodle interface on port 81. But people can't type 81 at the end of the addy . So we want to put moodle on 80..I think...so would your solution do this?
or maybe I just want to be a pineapple
You're spot on Witch, you have IIS on your current IP on port 80 and to avoid people adding :81 to their url you would add a secondary IP to the server and bind Apache on port 80 to that and in turn bind IIS on the old IP on port 80 otherwise IIS (and apache in fairness) will by default try and use all IPs.
Witch.. what I would suggest you do is this:
I presume you have more than one dns hostname.. website would be www.schoolname.county.sch.uk and moodle would be moodle.schoolname.county.sch.uk - if this isnt the case, and moodle is usually accessed at www.schoolname.county.sch.uk:81 [same DNS as the website], you will need to get an additional dns host added [probably at the LEA].
Since one of the earlier release of the HTTP specification, you can redirect based on hostname - ie: moodle.schetc and www.schetc can be directed to different places despite being on the same ip and port. What I would suggest is that you move Apache onto port 80, and IIS onto 81. You can then configure apache to 'proxy' any requests sent to www.schetc across to IIS and handle moodle itself.
You can add lines similar to this to Apache:
CustomLog logs/access_log common
ProxyPass / http://localhost:81/
ProxyPassReverse / http://localhost:81/
CustomLog logs/moodle.schetc_access_log common
A good time to do this would be as part of your server changeover.
So is matt40k and kmount's solution the same as kyle williamsons?
I'm not sure if I need to add another IP to the server (where would I get this?) or get another DNS hostname?
This learning curve is becoming a bit Everest
Not sure kylewilliamson method would work.
Basically IIS and Apache can't share the same port.
Witch, is the server 2008? If you put a new server on the network, where would you get the IP address from?
Two websites can't share the same IP address and port. It causes fun stuff to happen.
However they can have different IP addresses and the same port, or different ports and the same IP address.
Just trying to clarify as I think poor witch is getting a bit boggled.
So adding another IP address will let you put the moodle site on that (new) address, and on port 80. You'll then need to get any requests for the moodle site going to that IP address by getting a DNS record set up to point at it.
That's probably the simplest way to do it, and it avoids having to move to IIS where you'd still need to add another IP address.
Two websites can, two webservers can't though.Two websites can't share the same IP address and port. It causes fun stuff to happen.
I agree, the easiest solution would be to add an additional IP address, tell apache to use that one, tell IIS to use the old one.
You are all saying different things again!
Yes we are moving to Server 2008 and presumably will use the same IP address as the current server - we only have one, and will continue to only have one!
So, basically I need a new IP address and tell apache to use that one for moodle, and IIS to use the old one for the website....
How do I get a new IP address? (obviously we have a range -can I just pick an unused one?)
Do I need the DNS bit?
Please can I have EXACT instructions on how to set up the system so that this will work. Words of one syllable please guys, with instructions on how to find the various bits I need written out step by step with no bits left out.
Frightened of breaking my bosses new lovely Moodle site? Me? Never!
There are currently 1 users browsing this thread. (0 members and 1 guests)