Hi Is it possible to use the full administration interface remotely through a web browser. It just seems that when I log in from remote I only get a limited interface even if I log in as koha_library But if I log in through lynx locally, also using koha_library, I get more administration menus and stuff. Thanks
What is your koha version and distro? -- Riley Childs Senior Charlotte United Christian Academy IT Services Administrator Library Services Administrator web: rileychilds.net twitter: @RowdyChildren cell: +1 (704) 497-2086 office: +1 (704) 537-0331 x101 lync: rchilds@cucawarriors.com (select external contact) -----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Ian D Sent: Monday, September 22, 2014 8:33 AM To: koha@lists.katipo.co.nz Subject: [Koha] full admin interface Hi Is it possible to use the full administration interface remotely through a web browser. It just seems that when I log in from remote I only get a limited interface even if I log in as koha_library But if I log in through lynx locally, also using koha_library, I get more administration menus and stuff. Thanks _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Koha 3.16.03.000 Linux Distro Ubuntu 12.04.5 LTS Thanks
From: rchilds@cucawarriors.com To: duxbuz@hotmail.com; koha@lists.katipo.co.nz Subject: RE: [Koha] full admin interface Date: Mon, 22 Sep 2014 13:26:52 +0000
What is your koha version and distro?
-- Riley Childs Senior Charlotte United Christian Academy IT Services Administrator Library Services Administrator web: rileychilds.net twitter: @RowdyChildren cell: +1 (704) 497-2086 office: +1 (704) 537-0331 x101 lync: rchilds@cucawarriors.com (select external contact)
-----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Ian D Sent: Monday, September 22, 2014 8:33 AM To: koha@lists.katipo.co.nz Subject: [Koha] full admin interface
Hi
Is it possible to use the full administration interface remotely through a web browser.
It just seems that when I log in from remote I only get a limited interface even if I log in as koha_library
But if I log in through lynx locally, also using koha_library, I get more administration menus and stuff.
Thanks
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Is it possible to use the full administration interface remotely through a web browser.
Yes, that's the only way to use the administration interface.
It just seems that when I log in from remote I only get a limited interface even if I log in as koha_library
Limited in what way? Perhaps you could post a screenshot somewhere and send us a link. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
Hi Am no closer with this.
Yes, that's the only way to use the administration interface. The only way I can use the interface is through a lynx browser logged into the library server (local login)
Limited in what way? When I use a remote machine I can only access a limited interface, there is no administration menu etc
Date: Tue, 23 Sep 2014 08:01:05 -0400 From: oleonard@myacpl.org To: koha@lists.katipo.co.nz Subject: Re: [Koha] full admin interface
Is it possible to use the full administration interface remotely through a web browser.
Yes, that's the only way to use the administration interface.
It just seems that when I log in from remote I only get a limited interface even if I log in as koha_library
Limited in what way? Perhaps you could post a screenshot somewhere and send us a link.
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Am no closer with this.
Yes, because we still don't understand the problem you're having.
When I use a remote machine I can only access a limited interface, there is no administration menu etc
It might help if we could see what you're seeing. Perhaps you could post a screenshot somewhere and send us a link. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
Yes, because we still don't understand the problem you're having.
And I thought I was writing the most verbose explanation the mailing list has ever seen!
Perhaps you could post a screenshot somewhere and send us a link.
A picture it is then! http://i1025.photobucket.com/albums/y319/duxbuz/issuekoha_zps538f4db5.jpg
Date: Tue, 23 Sep 2014 08:42:03 -0400 From: oleonard@myacpl.org To: koha@lists.katipo.co.nz Subject: Re: [Koha] full admin interface
Am no closer with this.
When I use a remote machine I can only access a limited interface, there is no administration menu etc
It might help if we could see what you're seeing.
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Greetings, That's the OPAC interface. You're apache settings are such that if it doesn't match the server name when you connect, you'll get the OPAC. snippets from /etc/apache2/sites-enabled/{instance name} ... ## OPAC <VirtualHost *:443> ... ServerName demo.library.kohasystem.ca ... </VirtualHost> ## Intranet <VirtualHost *:443> ... ServerName demo.library-admin.kohasystem.ca ... </VirtualHost> In the above example, I am running my development koha off of port 443 (https not http). ***NOTE: There are other things that make the https set up work, this example is not about https!*** Notice how I have the ServerName values set? Notice how OPAC is listed first? What do you think will happen if I go to https://{ip address for the machine}/? It will show OPAC, because: 1) {ip address for the machine} is not listed in any of my VirtualHost tags 2) {ip address for the machine} does not match any of the server names 3) the OPAC block *:443 matches first. You like have: 1) DNS not properly set up, or WRONGLY FAKED, and/or 2) You are trying to access a name-based install with an IP-based URL. GPML, Mark Tompsett
Thanks I had a feeling this was what the issue was. I will have a look at how I can get my IP based setup to work. My hostname does resolve using my local DNS server, but having it recognise a subdomain (or virtual host or what ever it is) I am unsure about That's a poor explanation. What I mean is if I type the name of my Ubuntu server into the browser it resolves e.g http://myubuntuserver, but if I typed admin-myubuntuserver or any sort of variation I do not know how to have this resolve I thought adding a ServerName admin-myubuntuserver in the /etc/apache2/sites-enabled/{instance name} is this all that's needed to fix this?
From: mtompset@hotmail.com To: duxbuz@hotmail.com CC: koha@lists.katipo.co.nz Subject: Re: [Koha] full admin interface Date: Tue, 23 Sep 2014 10:29:08 -0400
Greetings,
That's the OPAC interface. You're apache settings are such that if it doesn't match the server name when you connect, you'll get the OPAC.
snippets from /etc/apache2/sites-enabled/{instance name} ... ## OPAC <VirtualHost *:443> ... ServerName demo.library.kohasystem.ca ... </VirtualHost>
## Intranet <VirtualHost *:443> ... ServerName demo.library-admin.kohasystem.ca ... </VirtualHost>
In the above example, I am running my development koha off of port 443 (https not http). ***NOTE: There are other things that make the https set up work, this example is not about https!*** Notice how I have the ServerName values set? Notice how OPAC is listed first? What do you think will happen if I go to https://{ip address for the machine}/? It will show OPAC, because: 1) {ip address for the machine} is not listed in any of my VirtualHost tags 2) {ip address for the machine} does not match any of the server names 3) the OPAC block *:443 matches first.
You like have: 1) DNS not properly set up, or WRONGLY FAKED, and/or 2) You are trying to access a name-based install with an IP-based URL.
GPML, Mark Tompsett
OK great I changed the sites-available/{instance} to have the intranet ServerName have the value of my server and it worked.
From: duxbuz@hotmail.com To: mtompset@hotmail.com Date: Tue, 23 Sep 2014 15:14:13 +0000 CC: koha@lists.katipo.co.nz Subject: Re: [Koha] full admin interface
Thanks
I had a feeling this was what the issue was.
I will have a look at how I can get my IP based setup to work.
My hostname does resolve using my local DNS server, but having it recognise a subdomain (or virtual host or what ever it is) I am unsure about
That's a poor explanation. What I mean is if I type the name of my Ubuntu server into the browser it resolves e.g http://myubuntuserver, but if I typed admin-myubuntuserver or any sort of variation I do not know how to have this resolve
I thought adding a ServerName admin-myubuntuserver in the /etc/apache2/sites-enabled/{instance name} is this all that's needed to fix this?
From: mtompset@hotmail.com To: duxbuz@hotmail.com CC: koha@lists.katipo.co.nz Subject: Re: [Koha] full admin interface Date: Tue, 23 Sep 2014 10:29:08 -0400
Greetings,
That's the OPAC interface. You're apache settings are such that if it doesn't match the server name when you connect, you'll get the OPAC.
snippets from /etc/apache2/sites-enabled/{instance name} ... ## OPAC <VirtualHost *:443> ... ServerName demo.library.kohasystem.ca ... </VirtualHost>
## Intranet <VirtualHost *:443> ... ServerName demo.library-admin.kohasystem.ca ... </VirtualHost>
In the above example, I am running my development koha off of port 443 (https not http). ***NOTE: There are other things that make the https set up work, this example is not about https!*** Notice how I have the ServerName values set? Notice how OPAC is listed first? What do you think will happen if I go to https://{ip address for the machine}/? It will show OPAC, because: 1) {ip address for the machine} is not listed in any of my VirtualHost tags 2) {ip address for the machine} does not match any of the server names 3) the OPAC block *:443 matches first.
You like have: 1) DNS not properly set up, or WRONGLY FAKED, and/or 2) You are trying to access a name-based install with an IP-based URL.
GPML, Mark Tompsett
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Greetings,
My hostname does resolve using my local DNS server, Ask the person responsible for the DNS to add the appropriate name and ip to it. What I mean is if I type the name of my Ubuntu server into the browser it resolves e.g http://myubuntuserver, but if I typed admin-myubuntuserver or any sort of variation I do not know how to have this resolve Which browser, what machine? You are not providing enough details. There is a way to do it incorrectly, that will work. I would rather not post it, since it would encourage its abuse. I thought adding a ServerName admin-myubuntuserver in the /etc/apache2/sites-enabled/{instance name} is this all that's needed to fix this? No... there are two-sides. The client side and the server side. http://whatever in your browser is client side. It needs to be able to figure out the IP address through DNS lookup and then go talk to that machine using the HTTP protocol on port 80. This means some machine somewhere (the DNS server – or the ugly hack on only your local machine which is why you should not do it!) needs to know this information. When then client starts talking to the server machine, it tells it that it is looking for the URL you typed. Apache figures out what the client means and passes something back. This is where ServerName comes in. That’s the server knowing how to answer back. It isn’t the client knowing who to talk to in the first place. GPML, Mark Tompsett
participants (4)
-
Ian D -
Mark Tompsett -
Owen Leonard -
Riley Childs