On 3/26/20 12:40 PM, Ted To wrote:
> Thank you -- I added two lines to the hba file to allow for ident
> authentication, restarted postgres and still the same errors.
Without knowing how the client is trying to connect to the server this
issue will be difficult to solve.
>
> On 3/26/20 3:35 PM, Ron wrote:
>> You're only allowing "trust" authentication, not "ident" authentication.
>>
>> On 3/26/20 2:29 PM, Ted To wrote:
>>>
>>> Hi,
>>>
>>> I'm trying to configure miniflux and am struggling to figure out how
>>> to configure postgres for that purpose. (The miniflux instructions
>>> are very terse.) Regardless of whether I run the command as the
>>> postgres user or the miniflux user, I get similar errors. I am
>>> running Centos 7 using the updated scl version of postgres (9.6.10).
>>>
>>> With the following, the postgres user "miniflux" along with the
>>> password are specified in /etc/miniflux.conf.
>>>
>>> $ miniflux -c /etc/miniflux.conf -migrate
>>> Current schema version: 0
>>> Latest schema version: 26
>>> Migrating to version: 1
>>> [FATAL] [Migrate] pq: Ident authentication failed for user "miniflux"
>>>
>>> I have no problems logging into postgres as the miniflux user using
>>> the same password specified in /etc/miniflux.conf.
>>>
>>> Running the same command without specifying the configuration file
>>> uses the postgres user and also fails
>>>
>>> $ miniflux -migrate
>>> [INFO] The default value for DATABASE_URL is used
>>> Current schema version: 0
>>> Latest schema version: 26
>>> Migrating to version: 1
>>> [FATAL] [Migrate] pq: Ident authentication failed for user "postgres"
>>>
>>> My /var/opt/rh/rh-postgresql96/lib/pgsql/data/pg_hba.conf file includes
>>>
>>> # TYPE DATABASE USER ADDRESS METHOD
>>>
>>> local miniflux miniflux trust
>>> local miniflux postgres trust
>>>
>>> # "local" is for Unix domain socket connections only
>>> local all all peer
>>> # IPv4 local connections:
>>> host all all 127.0.0.1/32 trust
>>>
>>> I'm at a complete loss.
>>>
>>> Any suggestions?
>>>
>>> Thanks,
>>>
>>> Ted To
>>>
>>
--
Adrian Klaver
adrian.klaver@aklaver.com