Hello, Since i've upgraded for koha 3.8, i can't access on my opac. I think my virtualhost is good (i join it in attached file) but maybe there's something wrong i've not seen. I've the same url with two differents ports. For the intranet, it's ok but for the opac, it's the problem. thank you. samuel
Le 29/05/2012 14:15, Robin Sheat a écrit :
Op 29-05-12 23:55, Samuel Desseaux schreef:
I've the same url with two differents ports. For the intranet, it's ok but for the opac, it's the problem. You never said what your problem is.
Robin.
When i want go to the intranet (koha.ecp.fr:8080), everything is ok. When i want to go on the opac (koha.ecp.fr:80), i've this message " It works! This is the default web page for this server. The web server software is running but no content has been added, yet." Maybe it's a dns issue or something else?
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
On Tue, May 29, 2012 at 02:22:19PM +0200, Samuel Desseaux wrote:
Le 29/05/2012 14:15, Robin Sheat a écrit :
Op 29-05-12 23:55, Samuel Desseaux schreef:
I've the same url with two differents ports. For the intranet, it's ok but for the opac, it's the problem. You never said what your problem is.
Robin.
When i want go to the intranet (koha.ecp.fr:8080), everything is ok.
When i want to go on the opac (koha.ecp.fr:80), i've this message "
It works!
This is the default web page for this server.
The web server software is running but no content has been added, yet."
Maybe it's a dns issue or something else?
Hello Samuel, The address http://koha.ecp.fr/ works (for me): i could access your opac... (using internet: I hope is wanted) So it should be a network problem (dns / port-forwarding / ...) Do you use *exactly* http://koha.ecp.fr/ ? (and not an ip or another network name, for example) The virtual-host works like it: - when a connection arrived to apache (so your browser need to know an IP address [generally resolved by dns]) - the server check the "Host:" header (presented by the browser) to determine which virtual-host the browser request The page "it works" is the default page (so match, when no other virtual-host match) An other point, the intranet is accessible over internet too (when adding :8080 to the URL). You could (should ?) restrict this access to "trusted" IP/address (with "accept/deny from" apache configuration directive at minimum). -- Frère Sébastien Marie Abbaye Notre Dame de La Trappe 61380 Soligny-la-Trappe Web: http://www.latrappe.fr/
Le 29/05/2012 14:57, Frère Sébastien Marie a écrit :
On Tue, May 29, 2012 at 02:22:19PM +0200, Samuel Desseaux wrote:
Le 29/05/2012 14:15, Robin Sheat a écrit :
Op 29-05-12 23:55, Samuel Desseaux schreef:
I've the same url with two differents ports. For the intranet, it's ok but for the opac, it's the problem. You never said what your problem is.
Robin. When i want go to the intranet (koha.ecp.fr:8080), everything is ok.
When i want to go on the opac (koha.ecp.fr:80), i've this message "
It works!
This is the default web page for this server.
The web server software is running but no content has been added, yet."
Maybe it's a dns issue or something else?
Hello Samuel,
The address http://koha.ecp.fr/ works (for me): i could access your opac... (using internet: I hope is wanted)
So it should be a network problem (dns / port-forwarding / ...)
Do you use *exactly* http://koha.ecp.fr/ ? (and not an ip or another network name, for example)
The virtual-host works like it: - when a connection arrived to apache (so your browser need to know an IP address [generally resolved by dns]) - the server check the "Host:" header (presented by the browser) to determine which virtual-host the browser request
The page "it works" is the default page (so match, when no other virtual-host match)
An other point, the intranet is accessible over internet too (when adding :8080 to the URL). You could (should ?) restrict this access to "trusted" IP/address (with "accept/deny from" apache configuration directive at minimum).
Thank you, it's a problem in my office. For the intranet, i've planned it and do asap.
Le 29/05/2012 14:57, Frère Sébastien Marie a écrit :
The address http://koha.ecp.fr/ works (for me): i could access your opac... (using internet: I hope is wanted)
So it should be a network problem (dns / port-forwarding / ...) could is be a ridiculous caching problem: firefox (or a proxy) thinking he don't need to query Apache again, and you see the old initial page ?
-- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
At 03:07 PM 5/29/2012 +0200, Paul Poulain wrote:
Le 29/05/2012 14:57, Frère Sébastien Marie a écrit :
The address http://koha.ecp.fr/ works (for me): i could access your opac... (using internet: I hope is wanted)
So it should be a network problem (dns / port-forwarding / ...) could is be a ridiculous caching problem: firefox (or a proxy) thinking he don't need to query Apache again, and you see the old initial page ?
When we are in testing/maintenance/upgrade mode, we systematically use all browsers (FF, Opera, Chrome, Safari and limited IE) with cache disabled (or set to zero.) Doesn't everyone do this? We occasionally disable memcached also (although the variations and permutations on Apache 2.4 can be challenging.) A slightly more complex matter is if any intermediate proxy uses Squid, which can cache DNS as well as content. Best - P.
Yes, we use Firefox with cache disabled. (One may use WebDeveloper extension to do so). DNS cache may still exist but a simple close/reopen resolves the problem I think. On Tue, May 29, 2012 at 3:29 PM, Paul <paul.a@aandc.org> wrote:
At 03:07 PM 5/29/2012 +0200, Paul Poulain wrote:
Le 29/05/2012 14:57, Frère Sébastien Marie a écrit :
The address http://koha.ecp.fr/ works (for me): i could access your opac... (using internet: I hope is wanted)
So it should be a network problem (dns / port-forwarding / ...) could is be a ridiculous caching problem: firefox (or a proxy) thinking he don't need to query Apache again, and you see the old initial page ?
When we are in testing/maintenance/upgrade mode, we systematically use all browsers (FF, Opera, Chrome, Safari and limited IE) with cache disabled (or set to zero.) Doesn't everyone do this? We occasionally disable memcached also (although the variations and permutations on Apache 2.4 can be challenging.) A slightly more complex matter is if any intermediate proxy uses Squid, which can cache DNS as well as content.
Best - P. ______________________________**_________________ Koha-devel mailing list Koha-devel@lists.koha-**community.org<Koha-devel@lists.koha-community.org> http://lists.koha-community.**org/cgi-bin/mailman/listinfo/**koha-devel<http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel> website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.**org/ <http://bugs.koha-community.org/>
-- Fridolyn SOMERS fridolyn.somers@gmail.com Marsillargues - France <fridolyn.somers@gmail.com>
Hie, You must desactivate the Apache default website on port 80. Look into /etc/apache2/sites-enabled/. If you see file named "default", do : "sudo a2dissite default" and "sudo apache2ctl reload". It will reload apache configuration, do not use it in production. If doesn't work, look at who listens to 80 port with : "netstat". Regards, On Tue, May 29, 2012 at 2:57 PM, Frère Sébastien <semarie-koha@latrappe.fr>wrote:
On Tue, May 29, 2012 at 02:22:19PM +0200, Samuel Desseaux wrote:
Le 29/05/2012 14:15, Robin Sheat a écrit :
Op 29-05-12 23:55, Samuel Desseaux schreef:
I've the same url with two differents ports. For the intranet, it's ok but for the opac, it's the problem. You never said what your problem is.
Robin.
When i want go to the intranet (koha.ecp.fr:8080), everything is ok.
When i want to go on the opac (koha.ecp.fr:80), i've this message "
It works!
This is the default web page for this server.
The web server software is running but no content has been added, yet."
Maybe it's a dns issue or something else?
Hello Samuel,
The address http://koha.ecp.fr/ works (for me): i could access your opac... (using internet: I hope is wanted)
So it should be a network problem (dns / port-forwarding / ...)
Do you use *exactly* http://koha.ecp.fr/ ? (and not an ip or another network name, for example)
The virtual-host works like it: - when a connection arrived to apache (so your browser need to know an IP address [generally resolved by dns]) - the server check the "Host:" header (presented by the browser) to determine which virtual-host the browser request
The page "it works" is the default page (so match, when no other virtual-host match)
An other point, the intranet is accessible over internet too (when adding :8080 to the URL). You could (should ?) restrict this access to "trusted" IP/address (with "accept/deny from" apache configuration directive at minimum).
-- Frère Sébastien Marie Abbaye Notre Dame de La Trappe 61380 Soligny-la-Trappe Web: http://www.latrappe.fr/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Fridolyn SOMERS fridolyn.somers@gmail.com Marsillargues - France <fridolyn.somers@gmail.com>
participants (6)
-
Fridolyn SOMERS -
Frère Sébastien Marie -
Paul -
Paul Poulain -
Robin Sheat -
Samuel Desseaux