Dear colleagues,
I'm having a problem running my Creatio local environment when use PostgreSQL.
When start the app, I'm getting this error Exception Details: Npgsql.PostgresException: 28000: no hay una l�nea en pg_hba.conf para �fe80::1c5:206f:bef4:e3e9%13�, usuario �dev-toledano�, base de datos �Toledano8010�, sin cifrado
I have app and db in the same machine.
I saw I need to change the pg_hba.conf file, I did it, but get the same error. This is my file
# TYPE DATABASE USER ADDRESS METHOD
#host all all 0.0.0.0/0 trust
# "local" is for Unix domain socket connections only
local all all trust
#scram-sha-256
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# Allow replication connections from localhost, by a user with the
# replication privilege.
local replication all trust
host replication all 127.0.0.1/32 trust
host replication all ::1/128 trustAnd my ConnectionStrings.config file looks like
<?xml version="1.0" encoding="utf-8"?>
Somebody have some idea?
I never worked with PostgreSQL before
Thanks in advance,
Best regards
Like
local all postgres peer
# TYPE DATABASE USER ADDRESS METHOD
# "local" is for Unix domain socket connections only
local all all peer
# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
local replication all peer
host replication all 127.0.0.1/32 md5
host replication all ::1/128 md5
host all all 10.0.0.0/24 trustHere is Mine, maybe you need an "Host all all " and your local subnet?
Hello,
Here are some recommendations:
- Update your
pg_hba.conffile with the following content:
local all all trust
host all all 127.0.0.1/32 trust
host all all ::1/128 trust
-
Verify that your connection string in the
ConnectionStrings.configfile is accurate, including theServer,Port,Database,User ID, andPasswordsettings. -
Restart PostgreSQL after updating
pg_hba.confusing the command:sudo service postgresql restart. -
Test your connection to ensure the error is resolved.