Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

StackOverflow Point

StackOverflow Point Navigation

  • Web Stories
  • Badges
  • Tags
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Web Stories
  • Badges
  • Tags
Home/ Questions/Q 1812
Alex Hales
  • 0
Alex HalesTeacher
Asked: May 31, 20222022-05-31T03:12:43+00:00 2022-05-31T03:12:43+00:00

ruby on rails – Heroku ECONNREFUSED error: can deploy and set variables but can’t run console commands

  • 0

[ad_1]

I’m on Ubuntu 20, working on a Rails 7 project. I’ve succesfully created a Heroku app using heroku create appname and then deployed the Rails app using git push heroku master.

The app/website is accessible and works fine on Heroku, but I’m not being able to run most console commands using the Heroku cli.

I can deploy as described above, and also set environment variables via heroku config:set TWILIO_KEY='123', but commands like heroku run rails db:migrate, heroku run rails console and most if not any other commands that I try to run via heroku run command return the following error (IP changes every time):

Running rails console on ⬢ appname... done
Error: connect ECONNREFUSED 54.175.164.234:5000

Right after I run any of these commands from my console, I can see the app logs on Heroku updating accordingly and throwing an error.

For example, for the heroku run rails console command executed above, the app logs show:

2022-05-31T00:42:11.048694+00:00 app[api]: Starting process with command `rails console` by user [email protected]
2022-05-31T00:44:34.314621+00:00 heroku[run.6356]: Awaiting client
2022-05-31T00:44:34.307905+00:00 heroku[run.6356]: State changed from starting to up
2022-05-31T00:45:04.332589+00:00 heroku[run.6356]: Process exited with status 128
2022-05-31T00:45:04.332006+00:00 heroku[run.6356]: Error R13 (Attach error) -> Failed to attach to process
2022-05-31T00:45:04.389840+00:00 heroku[run.6356]: State changed from up to complete

The Heroku docs do not provide more information on R13 or status 128 error codes.

The error code itself does not provide any other information regarding the connection to what is failing either. Could it be the DB? The connection to Heroku itself is clearly not the problem.

Any help would be appreciated.

[ad_2]

  • 0 0 Answers
  • 1 View
  • 0 Followers
  • 0
Share
  • Facebook
  • Report
Leave an answer

Leave an answer
Cancel reply

Browse

Sidebar

Ask A Question

Related Questions

  • xcode - Can you build dynamic libraries for iOS and ...

    • 0 Answers
  • bash - How to check if a process id (PID) ...

    • 4997 Answers
  • database - Oracle: Changing VARCHAR2 column to CLOB

    • 1084 Answers
  • What's the difference between HEAD, working tree and index, in ...

    • 1028 Answers
  • Amazon EC2 Free tier - how many instances can I ...

    • 0 Answers

Stats

  • Questions : 43k

Subscribe

Login

Forgot Password?

Footer

Follow

© 2022 Stackoverflow Point. All Rights Reserved.

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.