- Posts: 64
- Joined: Thu Aug 08, 2019 3:40 pm
- Location: London UK
- Real Name: Bill Bulford
Thu Apr 08, 2021 5:14 pm
Install of new postgres machine / raid and Resolve 17.1.1 on Windows 10 with Win 10 clients
Tried to use a Resolve Studio install to install postgres, found it wasn't an option any more. Found new project server app on the support site and installed it. No help files found but seemed to install and as usual postgres is limited to local machine only ie no clients can find it. So went to pg_hba.conf in program files\ postgresxxx\data and appended 'host all all 0.0.0.0/0 md5' to open access up wide.
Discovered the share / don't share button on the server app which helpfully rewrites the pg_hba.conf file for you to open up access. Unfortunately it removes access for us. It left in the file just:
'host all all 127.0.0.1/32 md5 ' and
'host all all 10.130.1.6/24'
which cuts everyone off when postgres restarted. This server database connection goes out to a 1gig 10.150.xxx.xxx network where all the clients are found. There are two other closed 10gig networks on 10.130 .xx.xx from this machine to supply media to the clients. It had found one of those and used it. I put 0.0.0.0/0 back in and restarted postgres.
This server app either needs more intelligence or no share button at all as clicking it will cut everyone off and confuse anyone not in the know! You can of course configure pg_hba.conf and make it read only!
Tried to use a Resolve Studio install to install postgres, found it wasn't an option any more. Found new project server app on the support site and installed it. No help files found but seemed to install and as usual postgres is limited to local machine only ie no clients can find it. So went to pg_hba.conf in program files\ postgresxxx\data and appended 'host all all 0.0.0.0/0 md5' to open access up wide.
Discovered the share / don't share button on the server app which helpfully rewrites the pg_hba.conf file for you to open up access. Unfortunately it removes access for us. It left in the file just:
'host all all 127.0.0.1/32 md5 ' and
'host all all 10.130.1.6/24'
which cuts everyone off when postgres restarted. This server database connection goes out to a 1gig 10.150.xxx.xxx network where all the clients are found. There are two other closed 10gig networks on 10.130 .xx.xx from this machine to supply media to the clients. It had found one of those and used it. I put 0.0.0.0/0 back in and restarted postgres.
This server app either needs more intelligence or no share button at all as clicking it will cut everyone off and confuse anyone not in the know! You can of course configure pg_hba.conf and make it read only!