-
Notifications
You must be signed in to change notification settings - Fork 44
Unable to use pg-native on Node 10 on Heroku #71
Comments
(I'm working with @holm on this) Just did a bit more debugging. It's easily reproducible with a stock Ubuntu 16.04 and Node 10.4.1 using the binaries from nodejs.org. Then this simple script
fails with this error
It works on Ubuntu 18.04, where libpq is linked against a newer openssl version whereas on 16.04 it's using 1.0.2g (and node 10 is bundling 1.1.0h). Not quite sure though why/if the openssl upgrade in Node10 would affect pg-native? Isn't everything going directly to libpq and that handles the SSL connection itself? |
I’m pretty sure libpq and Node can’t use different OpenSSL versions. See #70 for the same issue in reverse. |
I just tried to upgrade to node-10 on my project which also uses heroku. We got the same error when trying to run db-migrate (which uses pg-natice on ssl-connections) on our production-database. Using node 9.x works fine. |
Is it possible to get this working on heroku with node 10? |
With node 10.13.0 I get this:
|
I'm having the same problem as @tapz on Fedora with Node 10 |
etting same problem on various versions of Node from 8 to 10.16 except 10.15.3 where the error is could not create SSL context: library has no ciphers. All this on AWS Elastic Beanstalk. The solution was to simply use pg instead of pg-native. |
hello. Could you help me? I used pg-native as option for pg-promise on node 8 it was working fine. |
I was able to get this working for Heroku and Node v12.13.1 by adding |
We have been using pg-native for years now without issues. We are now upgrading to Node 10 and are running into problems. Using just
pg
works without issues, but withpg-native
we see this error when trying to connect to a db using ssl:could not create SSL context: library has no ciphers
It then fails to connect as we require SSL.
Versions
node: 10.4.1.
pg-native: 3.0.0
libpq: 1.8.8
openssl: 1.1.0g
Any ideas what could be wrong?
The text was updated successfully, but these errors were encountered: