The first problem is normal presuming you have not logged in as the postgres user. Your client is likely using the socket by default. The default pg_hba.conf (I think) has 'local all all peer' which does peer for users that are not postgres. Guessing you were logged in as normal user account or opensrf? You could change the local all all line to password or md5 depending on what you are doing. The line you included would only work for the local postgres user.
The second part isn't overly clear. If you don't have firewall issues with clients accessing port 7682 you do not need a proxy. If you want both evergreen web interface and the websockets served over the same 443 connection then you have to proxy the websocket 443 traffic in the background to 7682. Since this is just a test setup I don't think you need to bother unless you have UFW set to block all ports besides 80/443. You may want to disable ufw to see if your interface works fine with everything allowed. If you are using websocketd with --ssl then you will want to make sure you are loading an ssl cert on the command line that your browser will accept. If it blocks the SSL in the background you mostly just know by blank pages. Your browser devtools will help a lot to figure out where things are going wrong with the staff webclient. You should be able to see the 7682 traffic either blocked or not working depending on whether it is an SSL or server issue. Ryan Eby From: "JonGeorg SageLibrary" <[email protected]> To: "Evergreen Discussion Group" <[email protected]> Sent: Monday, January 6, 2020 1:23:24 PM Subject: [OPEN-ILS-GENERAL] Fresh install of Evergreen 3.4 assistance I need help installing a fresh copy of Evergreen 3.4 on an Ubuntu 16.04 test server. I've done this from scratch a few times now, trying different settings and keep getting errors. These are the basic steps I'm following. *Fresh install of 16.04 - I'm using 16.04 to emulate one of our other servers. - not installing postgres automatically, so I can install 9.6 for the same reason. *Install Postgres 9.6 *Install Apache - test page at the ip works in browser of another machine on same network *Install UFW *Install Python, node.js, Angular JS, NPM *Install OpenSRF, eJabberD *Install Evergreen 3.4.1 I have two issues that don't make sense. When I attempt to log into the database with "psql -U evergreen evergreen" as configured I get a FATAL peer authentication error - however if I login as "psql -U evergreen -h 127.0.0.1 evergreen" it works... The pg_hba.conf file has "local all postgres md5" - I even tried setting it to trust, running alter password, restarting postgres, switching it to md5, restarting postgres again, and same error. Ideas? Is this an error that matters for a test server and would affect the web client? The other issues I'm running into are primarily Apache based - I've made sure the ports are all open, but according to the instructions it gets murky regarding proxy or not since needing the web client, and whether that should be on 7682 or 443. I had it resolving the url to ip/eg/opac/home with a blank page for http but not https so therefore an issue with the self signed SSL certification, but now that isn't working either. Can someone assist? Thanks -Jon
