RocketChat / RocketChat/Rocket.Chat
Rocketchat on Heroku fails to bind to port within 60 seconds
Open
Nobody has claimed this yet.
deployment
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
I've had a Rocketchat that I've been using for a couple weeks
Now, when I'm on Heroku, it begins restoring things from cache, but it doesn't boot a server with a port that Heroku can bind to within 60s, and the app crashes.
Any good way around this on Heroku? Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by reproducing the Heroku deployment and observing cache restoration before the 60-second port-binding timeout; done means identifying a verified way for Rocket.Chat to bind its port within Heroku's limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100