'尝试访问heroku控制台时，您无法访问该应用程序'

本文介绍了'尝试访问heroku控制台时，您无法访问该应用程序'的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我最近开始使用Ruby on Rails在Heroku上进行项目合作。我被添加为协作者，并将遥控器添加到我的环境中。经过一些开发之后，我推出了一些更改并没有任何问题：

$ git push staging

其中staging是我的远程的名称。 后来，当试图在Heroku上运行rake test时，我收到一个错误： pre $ $ heroku run rake测试--app分段运行附加到终端的`rake test`失败！您无权访问应用程序分段。

这很奇怪，因为我完全可以推动自己的修改。我查看了Heroku仪表板，看到我的推送记录在那里。然后我尝试使用控制台查看日志，并发生相同的问题。

$ heroku日志--app分段！您无权访问应用程序分段。

最后，我尝试访问控制台，但也失败了。

$ heroku run rails console --app staging 运行连接到终端的`rails console`失败！您无权访问应用程序分段。

此时我更新了我的Heroku工具栏安装，并使用heroku auth验证我的电子邮件显示出来，但错误仍然存​​在。我目前正在联系Heroku支持，但我希望有类似问题的人可以帮助我平行。

谢谢！

解决方案

类似的问题，这是因为我将我的Heroku应用程序的名称与我的git遥控器的名称混合在一起。因此，当我调用--app staging（我的远程名称）时，我应该使用应用程序的实际名称，如Heroku中所示。

I recently started collaborating in a project on Heroku using Ruby on Rails. I was added as a collaborator and added the remote to my environment. After some development, I pushed some changes and had no problems:

$ git push staging

Where staging is the name of my remote. Later, when trying to run "rake test" on Heroku, I recieved an error:

$heroku run rake test --app staging Running `rake test` attached to terminal... failed ! You do not have access to the app staging.

Which is odd, as I was perfectly able to push my own changes. I checked the Heroku dashboard and saw that my push was logged there. I then tried to view the logs using the console, and the same problem occured.

$ heroku logs --app staging ! You do not have access to the app staging.

Finally, I tried to access the console, but it failed as well.

$ heroku run rails console --app staging Running `rails console` attached to terminal... failed ! You do not have access to the app staging.

At this point I updated my Heroku toolbelt installation, and used "heroku auth" to verify that my email was showing up, but the error persists. I'm currently contacting Heroku support but I'm hoping someone with a similar issue could aid me in parallel.

Thanks!

解决方案

So just in case anyone is having a similar problem, this occurs because I was mixing the name of my Heroku Apps with the name of my git remotes. So when I was calling --app staging (the name of my remote), I should have been using the actual name of the app, as found in Heroku.