Hi Melvin, When I make this entry
host replication rep 104.131.66.183/32 md5 It complains that it cannot have both CIDR and mask number and fails to start –– I assume it's referring to /32 –– and when I remove that it starts alright, but it doesn't accept replication connections from that IP address. (Also I changed REP_USER to "replication" in latest examples, but it's consistent in both master and slave.) | Did you remember to do: SELECT pg_reload_conf(); Yes, in a manner of speaking. The database is in a Docker container, so I'm recreating the container everytime I change something in the configuration. :) On Thu, Apr 9, 2015 at 3:20 PM, Melvin Davidson <melvin6...@gmail.com> wrote: > So did you make the following entry in pg_hba,conf? > > host replication rep 104.131.66.183/32 md5 > > Is rep a valid postgres user in the cluster? > > Did you remember to do: > SELECT pg_reload_conf(); > > After making the changes to pg_hba.conf? > > > On 4/9/15, Volkan Unsal <spockspla...@gmail.com> wrote: > > HI Adrian, > > > > > > > >> Can you connect remotely from the standby using psql? > > > > > > > > Yes, I can connect directly from the standby using psql and DB_USER and > > DB_PASS. > > > > > > > > > > -- > > *Volkan Unsal* > > *web and mobile development* > > volkanunsal.com <http://bit.ly/1h1ebjy> > > > > > -- > *Melvin Davidson* > I reserve the right to fantasize. Whether or not you > wish to share my fantasy is entirely up to you. > -- *Volkan Unsal* *web and mobile development* volkanunsal.com <http://bit.ly/1h1ebjy>
