I posted this problem to the list last May, and someone *must* have helped me solve it because I had this working for the last nine months. I had to migrate to new hardware and the same puzzle has resurfaced. I checked the archives, but cannot find the helpful reply anywhere so I assume the respondent must have re'd me only. I simply cannot remember what the fix was, so I post it again in hopes the answer may appear once more. ---------- Hello folks. I just successfully finished setting up KoHa on a Macintosh running 10.4 Tiger. When at the koha computer, I open a web page and type http://localhost and up pops the opac main page just like it should. However, accessing from a remote machine with http://172.16.1.11 brings up the Apache default page. To test locally, I went to the koha machine and double-checked the IP address, which is correctly 172.16.1.11, then tried http://172.16.1.11 right at the koha machine, and up came the Apache default page. Switching to the loopback IP, though, http://127.0.0.1 brings up KoHa. I even tried: http://172.16.1.11/cgi-bin/koha/opac-main.pl at the koha machine and got the "Not Found" response. So, it seems there is a setting in Apache that I missed. Any help, or pointing me in the right direction to help myself, would be greatly appreciated.
On Thu, 01 Feb 2007, Lawrence Bean wrote:
I posted this problem to the list last May, and someone *must* have helped me solve it because I had this working for the last nine months. I had to migrate to new hardware and the same puzzle has resurfaced. I checked the archives, but cannot find the helpful reply anywhere so I assume the respondent must have re'd me only.
Is this it? http://www.google.com/search?q=Lawrence%20Bean%20koha%20
Hi, On Thu, 01 Feb 2007, Gavin McCullagh wrote:
On Thu, 01 Feb 2007, Lawrence Bean wrote:
I posted this problem to the list last May, and someone *must* have helped me solve it because I had this working for the last nine months. I had to migrate to new hardware and the same puzzle has resurfaced. I checked the archives, but cannot find the helpful reply anywhere so I assume the respondent must have re'd me only.
Is this it?
Sorry that wasn't very helpful. It sounds like you need to create or modify a virtual host to point to koha -- the localhost one does now but the 172.16 address doesn't. I would generally have created a DNS name for the site (eg www.koha.local.net) and added a virtual host like this to my apache set up. I presume Koha probably comes with one but this example might be of some help. <VirtualHost 172.16.11.1:80> ServerAdmin webmaster@blah.blah ServerName www.koha.local.net ServerAlias koha.local.net DocumentRoot </path/to/koha> <Directory /path/to/koha/> Options Indexes FollowSymLinks MultiViews AllowOverride AuthConfig Order allow,deny allow from all </Directory> # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. LogLevel warn CustomLog /var/log/apache2/koha/access.log combined ErrorLog /var/log/apache2/koha/error_log ServerSignature On </VirtualHost> Gavin
Gavin McCullagh <gmccullagh@gmail.com> writes:
It sounds like you need to create or modify a virtual host to point to koha -- the localhost one does now but the 172.16 address doesn't.
Thank you, that was exactly it and the memories came tumbling back when I saw the words "virtual host". I had also changed the address when changing hardware which is why what I had done last time no longer worked. It was simply a matter of copying/pasting the existing <VirtualHost localhost:80> yadayadayada </VirtualHost> <VirtualHost localhost:8080> yadayadayada </VirtualHost> in /etc/koha-httpd.conf and changing the "localhost" to the new IPs and FQDNs I'm now using. Thank you so much, and the answer should now be archived in the archives!
participants (2)
-
Gavin McCullagh -
Lawrence Bean