Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Heroku Deploy Error #192

Closed
braebo opened this issue Jan 15, 2021 · 7 comments · Fixed by #199
Closed

Heroku Deploy Error #192

braebo opened this issue Jan 15, 2021 · 7 comments · Fixed by #199

Comments

@braebo
Copy link

braebo commented Jan 15, 2021

It seems the default Heroku config fails. All I did was click the button, name the app, then click deploy. I tried multiple times. Any advice?

Screenshot 2021-01-15 at 6 04 03 PM

@markmichon
Copy link
Contributor

Hi @fractalhq, very strange. On my first attempt I was able to reproduce the problem. Then I tried again, and it worked without an issue. I suspect there are some intermittent problems on Heroku's end when provisioning the db. Either way, give it another try and see if you still experience the issue.

@grey-cat-1908
Copy link

Yes, I have this error too. I tried to deploy 8 times, but I can't

@danielsvane
Copy link

Same issue, tried multiple times

@braebo
Copy link
Author

braebo commented Feb 7, 2021

I've since tried again with no luck

@markmichon
Copy link
Contributor

markmichon commented Feb 7, 2021

Edit: Latest updates on master should fix this. If that isn't the case, comment below.


Looking into this, as I am now able to reproduce. Sadly, heroku wipes the release phase log when it fails so it is increasingly hard to debug. At first glance, it looks SSL related. They've also made some updates to their postgres offerings in January, which lines up with when this issue popped up.

For anyone else trying to debug, you can fork this repo then use https://heroku.com/deploy?template=https://github.com/XXXXXX with your repo to trigger a heroku click build.

@jgillard
Copy link

jgillard commented Feb 10, 2021

I just hit this issue, and have already pulled master with your latest commit mentioned above.

I was going a git pull from GitHub and a git push to Heroku to trigger this.

> pizzly@0.2.0 db:migrate
> knex --cwd dist/src/lib/database/config migrate:latest
Using environment: production
FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
error: no pg_hba.conf entry for host "54.171.30.207", user "XXX", database "XXX", SSL off
    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:278:15)
    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29)
    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38)
    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:8:42)
    at Socket.emit (node:events:378:20)
    at addChunk (node:internal/streams/readable:313:12)
    at readableAddChunk (node:internal/streams/readable:288:9)
    at Socket.Readable.push (node:internal/streams/readable:227:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
npm ERR! code 1
npm ERR! path /app
npm ERR! command failed
npm ERR! command sh -c knex --cwd dist/src/lib/database/config migrate:latest
npm ERR! A complete log of this run can be found in:
npm ERR!     /app/.npm/_logs/2021-02-10T15_02_00_575Z-debug.log

@markmichon
Copy link
Contributor

I had a few issues trying to reproduce @jgillard. Maybe heroku was having issues earlier? The 'deploy to heroku' button works thought:

Screen Shot 2021-02-10 at 10 37 59 AM

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants