Re: [OPEN-ILS-GENERAL] Web Staff Client Won't Login
Thanks Jason, that gave me the information I needed to get it working. The websockets configuration file (/etc/apache2-websockets/apache2.conf) didn't have the appropriate SSL information, it was still set to the default values and websockets would not start as a result. Edited that file with the correct .crt and .key entries and websockets stars and the Web staff client is allowing login. Thanks again! Jesse McCarty City of Burlington Information Systems Technician -Original Message- From: Open-ils-general [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jason Stephenson Sent: Wednesday, May 09, 2018 11:53 AM To: open-ils-general@list.georgialibraries.org Subject: Re: [OPEN-ILS-GENERAL] Web Staff Client Won't Login On 05/09/2018 01:37 PM, Jesse McCarty wrote: > Netstat doesn't even show anything listening on the default websockets port. That sounds like the websockets instance of Apache is not running. What does # apache2ctl-websockets start output? Note: the # means you should run it as root or via sudo. Jason
Re: [OPEN-ILS-GENERAL] Web Staff Client Won't Login
On 05/09/2018 01:37 PM, Jesse McCarty wrote: > Netstat doesn't even show anything listening on the default websockets port. That sounds like the websockets instance of Apache is not running. What does # apache2ctl-websockets start output? Note: the # means you should run it as root or via sudo. Jason
Re: [OPEN-ILS-GENERAL] Web Staff Client Won't Login
Thanks for the information everyone. It appears I have everything in place on the firewall configurations but still no go. Netstat doesn't even show anything listening on the default websockets port. I also tried setting up the NGINX proxy in the OpenSRF instructions and with that in place the web staff client goes into offline mode. Jesse McCarty City of Burlington Information Systems Technician -Original Message- From: Open-ils-general [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jason Stephenson Sent: Tuesday, May 08, 2018 5:22 AM To: open-ils-general@list.georgialibraries.org Subject: Re: [OPEN-ILS-GENERAL] Web Staff Client Won't Login On 05/07/2018 10:12 PM, Blake Henderson wrote: > That behavior usually means that the browser cannot connect to the > server on port 7682. Check to make sure that your browser can talk to > the server on that port by using this special URL: > > https://yourservername.org:7682 I am going to add that the above is necessary with Firefox if you use a self-signed certificate. Firefox seems to track certificates by server name and port number. So, you'll have to go to that URL and make the security exception for its certificate, too. You will also have to do this every time you change certificates on the server as well. I have not had to do the above with Chromium, and I hear it is not necessary with Chrome, either. You can also avoid the whole mess by setting up a proxy server, which may be overkill for a test installation, but is a good idea for production. Jason
Re: [OPEN-ILS-GENERAL] Web Staff Client Won't Login
On 05/07/2018 10:12 PM, Blake Henderson wrote: > That behavior usually means that the browser cannot connect to the > server on port 7682. Check to make sure that your browser can talk to > the server on that port by using this special URL: > > https://yourservername.org:7682 I am going to add that the above is necessary with Firefox if you use a self-signed certificate. Firefox seems to track certificates by server name and port number. So, you'll have to go to that URL and make the security exception for its certificate, too. You will also have to do this every time you change certificates on the server as well. I have not had to do the above with Chromium, and I hear it is not necessary with Chrome, either. You can also avoid the whole mess by setting up a proxy server, which may be overkill for a test installation, but is a good idea for production. Jason
Re: [OPEN-ILS-GENERAL] Web Staff Client Won't Login
Jesse, That behavior usually means that the browser cannot connect to the server on port 7682. Check to make sure that your browser can talk to the server on that port by using this special URL: https://yourservername.org:7682 be sure and notice that the URL is httpS If that page doesn't load, then check the firewall(s) between you and the server. -Blake- Conducting Magic MOBIUS On 5/7/2018 5:24 PM, Jesse McCarty wrote: Hello Everyone, We recently upgraded to the 3.0 series of Evergreen (3.0.6) and are looking at testing out the web client, but it won’t login. I went through the OpenSRF install instructions with the websockets extras and can get to the /eg/staff login page, but clicking on sign in or pressing enter does nothing. Did I miss a step in the install/upgrade somewhere along the line? It also doesn’t show any of the custom color schemes of each library, instead staying green – not sure if this is by design or if I have something missing. Thanks in advance, Jesse McCarty City of Burlington Information Systems Technician
