question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Regression in 7.18.0 causing "unsupported frontend protocol 1234.5679: server supports 2.0 to 3.0"

See original GitHub issue

I don’t use pg directly but through sequelize (ORM). Updating to 7.17.0 works fine. 7.17.1 works fine, but the same unchanged code with pg 7.18.0 will throw an exception on connection:

unsupported frontend protocol 1234.5679: server supports 2.0 to 3.0

I don’t have the full exception atm but this bit:

at Connection.connectingErrorHandler (C:\Users\jant\Repos\get-coffee\packages\get-coffee-api\node_modules\pg\lib\client.js:194:14)
    at Connection.emit (events.js:210:5)
    at Connection.EventEmitter.emit (domain.js:476:20)
    at TLSSocket.<anonymous> (C:\Users\jant\Repos\get-coffee\packages\get-coffee-api\node_modules\pg\lib\connection.js:144:12)
    at TLSSocket.emit (events.js:210:5)
    at TLSSocket.EventEmitter.emit (domain.js:476:20)
    at addChunk (_stream_readable.js:308:12)
    at readableAddChunk (_stream_readable.js:289:11)
    at TLSSocket.Readable.push (_stream_readable.js:223:10)
    at TLSWrap.onStreamRead (internal/stream_base_commons.js:182:23)

Why do I believe this is a regression: After downgrading to 7.17.1, connection works fine. After upgrading to 7.18.0, it breaks again.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:10
  • Comments:18 (11 by maintainers)

github_iconTop GitHub Comments

6reactions
brianccommented, Jan 30, 2020

alrighty everyone…published pg@7.18.1

sorry again for the disruption! Please don’t hesitate to open another issue if there’s something amiss. I’ll be watching for the next several hours at least. ❤️

5reactions
brianccommented, Jan 29, 2020

found the problem, and tested a fix. figuring out a unit test for it & will push a new patch version w/ the fix. my deep apologies!

Read more comments on GitHub >

github_iconTop Results From Across the Web

psycopg2.OperationalError: FATAL: unsupported frontend ...
1234.5679 is the special code sent by the client to request SSL-encrypted database connections, and support for that has been in PostgreSQL ...
Read more >
703242 – dev-db/postgresql-12.1 client failing to connect to ...
... error: could not connect to server: FATAL: unsupported frontend protocol 1234.5679: server supports 2.0 to 3.0 Expected Results: Should ...
Read more >
Postgres “unsupported frontend protocol” mystery
Before we go into the specific error, let's review what causes this particular message to appear.
Read more >
BCA-Networks.log.0 shows PostgreSQL error: unsupported ...
log.0 shows PostgreSQL error: unsupported frontend protocol 1234.5680: server supports 2.0 to 3.0. TrueSight Network Automation ...
Read more >
Python – psycopg2.OperationalError: FATAL: unsupported ...
OperationalError: FATAL: unsupported frontend protocol 1234.5679: server supports 2.0 to 3.0. postgresqlpsycopg2python. I'm using Macbook.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found