[Koha] Installed new server can no longer access KOHA.

[Robin Sheat]

MJ Ray schreef op wo 20-05-2015 om 12:11 [+0100]:
> 418 These short instructions assume that the default site is
> 419 not needed.  Talk with your system administrator, network
> 420 administrator, or IT Department to CONFIRM THIS BEFORE RUNNING
> 421 the following command:
> 422     sudo a2dissite 000-default

This is not really good advice (though at least it has caveats), except
in the case of doing IP-based addressing.

If you're doing virtual host-based addressing (which is normal), and you
get the default "It works!" page, then you need to fix your
configuration[0]. If removing the default site makes things work, then
you're papering over a real issue and it's quite likely that relying on
this will break when something changes in the future.

So, don't disable the default site just to make Koha work: fix your
apache configuration for Koha instead. And stop telling people to
disable the default site to make it work. It's bad practice[1].

http://i.imgur.com/V3hUcpX.png

Footnotes:

[0] In particular, you don't have a ServerName or ServerAlias parameter
that matches the hostname that you're trying to use specified
in /etc/apache2/sites-enabled/library.conf

[1] Unless you're doing IP-based addressing, but you should only do that
if you really have no other choice as expecting people to memorise IP
addresses sucks.

-- 
Robin Sheat
Catalyst IT Ltd.
✆ +64 4 803 2204
GPG: 5FA7 4B49 1E4D CAA4 4C38  8505 77F5 B724 F871 3BDF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part
URL: <https://lists.katipo.co.nz/pipermail/koha/attachments/20150521/838b40ad/attachment.sig>