Heroku Error: self-signed certificate SSL fix #6050
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexandrebodin
added
source: core:database
Codecov Report
@@ Coverage Diff @@
## documentation #6050 +/- ##
==============================================
Coverage 19.13% 19.13%
==============================================
Files 855 855
Lines 11934 11934
Branches 1898 1898
==============================================
Hits 2284 2284
Misses 8101 8101
Partials 1549 1549
Continue to review full report at Codecov.
|
Heroku Error: self-signed certificate SSL fix for PG '^8.0.0'. Setting SSL options to `"ssl": { "rejectUnauthorized": false }` enables SSL but does not reject self-signed certificate for Heroku deployment. The issue occurs when Heroku invokes node application but fails at SSL cert for PG ^8.0.0.
Signed-off-by: Kelvin Tsoi <ktsoi@wearfigs.com>
|
Props to the whole Strapi team and contributors for such an amazing project! |
This was referenced May 5, 2020
alexdevmotion
pushed a commit
to alexdevmotion/strapi
that referenced
this pull request
Jun 6, 2020
Heroku Error: self-signed certificate SSL fix for PG '^8.0.0'. Setting SSL options to `"ssl": { "rejectUnauthorized": false }` enables SSL but does not reject self-signed certificate for Heroku deployment. The issue occurs when Heroku invokes node application but fails at SSL cert for PG ^8.0.0.
Signed-off-by: Kelvin Tsoi <ktsoi@wearfigs.com>
Signed-off-by: Alexandru Constantin <alex@devmotion.ro>
|
This pull request has been mentioned on Strapi Community Forum. There might be relevant details there: https://forum.strapi.io/t/error-no-pg-hba-conf-entry-for-host-ssl-off/3409/1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Heroku Error: self-signed certificate SSL fix for PG '^8.0.0'. Setting SSL options to
"ssl": { "rejectUnauthorized": false }enables SSL but does not reject self-signed certificate for Heroku deployment. The issue occurs when Heroku invokes node application but fails at SSL cert for PG ^8.0.0.Description of what you did: