`gleam run -m squirrel` returns error "no pg_hba.conf entry for host"

[edkelly303]

Hi Jak!

I'm running into a new exciting error when trying to connect to my database with Squirrel v3.0.4:

➜  event_store git:(master) ✗ gleam run -m squirrel                                Compiled in 0.10s
    Running squirrel.main
Error: Cannot authenticate (no-method)

I ran into an unexpected problem while trying to authenticate with the Postgres
server. This is most definitely a bug!

Please open an issue at
https://github.com/giacomocavalieri/squirrel/issues/new with some
details about what you where doing, including the following message:
  Expected: AuthMethod, Got: BeErrorResponse(Set(dict.from_list([#(Code("28000"), []), #(File("auth.c"), []), #(Line("542"), []), #(Message("no pg_hba.conf entry for host \"XX.XXX.XXX.XX\", user \"XXXXXstaging\", database \"XXXXX__staging__2024-11-25_11-00\", no encryption"), []), #(Routine("ClientAuthentication"), []), #(Severity("FATAL"), []), #(SeverityLocalized("FATAL"), [])])))

I'm pretty sure this Postgres user/role has a SCRAM password, not an MD5 one, so it's (presumably) not the same issue that we spoke about at Lambda Days.

If helpful, I'm running Gleam 1.11.1 on WSL/Ubuntu on Windows 10, connecting to a remote Postgres 16.8 database, and my deps in gleam.toml are:

[dependencies]
gleam_stdlib = ">= 0.51.0 and < 2.0.0"
mist = ">= 4.0.0 and < 5.0.0"
gleam_erlang = ">= 0.33.0 and < 1.0.0"
gleam_http = ">= 4.0.0 and < 5.0.0"
gleam_otp = ">= 0.16.1 and < 1.0.0"
pog = ">= 3.0.0 and < 4.0.0"
envoy = ">= 1.0.2 and < 2.0.0"
gleam_json = ">= 3.0.0 and < 4.0.0"

[dev-dependencies]
gleeunit = ">= 1.0.0 and < 2.0.0"
squirrel = ">= 3.0.4 and < 4.0.0"

Ed.

[edkelly303]

I just realised that some extra context might be helpful here:

connecting to a remote Postgres 16.8 database

This is probably the weirdest thing I'm doing. For reasons, I am connecting to a remote Postgres database running in AWS RDS, rather than a local Postgres instance running on my own machine.

[giacomocavalieri]

You're right that's a new exciting error! 😄
I'll have to have a look at it and see if I can manage to replicate it, thanks for reporting!

[naomieow]

Running into this myself.
Squirrel 4.2.0, Gleam 1.12.0, Postgres 17.5

❯ gleam --version
gleam 1.12.0

❯ postgres --version
postgres (PostgreSQL) 17.5

❯ gleam run -m squirrel
   Compiled in 0.05s
    Running squirrel.main
Error: Cannot authenticate (no-method)

I ran into an unexpected problem while trying to authenticate with the Postgres
server. This is most definitely a bug!

Please open an issue at
https://github.com/giacomocavalieri/squirrel/issues/new with some
details about what you where doing, including the following message:
  Expected: AuthMethod, Got: BeErrorResponse(Set(dict.from_list([#(Code("28000"), []), #(File("auth.c"), []), #(Line("540"), []), #(Message("no pg_hba.conf entry for host \"127.0.0.1\", user \"postgres\", database \"daggerheart_api\", no encryption"), []), #(Routine("ClientAuthentication"), []), #(Severity("FATAL"), []), #(SeverityLocalized("FATAL"), [])])))

[dependencies]
gleam_stdlib = ">= 0.44.0 and < 2.0.0"
wisp = ">= 1.8.0 and < 2.0.0"
mist = ">= 5.0.3 and < 6.0.0"
gleam_erlang = ">= 1.3.0 and < 2.0.0"
gleam_http = ">= 4.1.1 and < 5.0.0"
gleam_json = ">= 3.0.2 and < 4.0.0"
pog = ">= 4.1.0 and < 5.0.0"

[dev-dependencies]
gleeunit = ">= 1.0.0 and < 2.0.0"
squirrel = ">= 4.2.0 and < 5.0.0"

[fruno-bulax]

My first suspicion would be that the "no pg_hba.conf entry" is, in fact, due to a missing entry in pg_hba.conf 😄
Particularly because this error occurs in direct response to the initial startup message, there isn't a whole lot to do wrong on the client side.

Could you have a look at the postgres docs (there are some good example entries at the bottom of the page) and post snippets of your config if that doesn't solve the issue?

[PLyn]

I ran into this issue too connecting to a remote Supabase postgres DB as well. Notably, it only happens when SSL is forced/enabled. Once I disable SSL, squirrel works fine via direct connection or via a connection pooler. From looking at similar issues, it looks like SSL isn't supported as yet sadly.

This is likely a different root cause from the others here but just adding this in case it helps.

Error message I got:
Expected: AuthMethod, Got: BeErrorResponse(Set(dict.from_list([#(Code("28000"), []), #(File("auth.c"), []), #(Line("541"), []), #(Message("no pg_hba.conf entry for host "[IP-ADDRESS-REDACTED]", user "postgres", database "postgres", no encryption"), []), #(Routine("ClientAuthentication"), []), #(Severity("FATAL"), []), #(SeverityLocalized("FATAL"), [])])))