Heroku,插件无法识别经过验证的帐户
我已通过输入我的账单信息在 Heroku 中验证了我的帐户。当我访问 http://heroku.com/confirm 时,它告诉我“您的帐户已验证”。
但是,当我运行命令来添加附加组件(例如 heroku addons:add custom_domains
)时,我收到此错误:
-----> Adding custom_domains to uplate... failed
! Please verify your account to install this add-on
! For more information, see http://devcenter.heroku.com/categories/billing
! Confirm now at https://heroku.com/confirm
此外,当我单击网站上的任何“验证”链接时(例如在附加页面上),我只是被重定向到我所在的同一页面,但它一直告诉我进行验证。
我错过了什么吗?这是我在 Heroku 上的第一个应用程序,所以我仍然有点困惑。
I've verified my account in Heroku by entering my billing information. When I visit http://heroku.com/confirm, it tells me "Your account is already verified".
However, when I run a command to add an add-on, such as heroku addons:add custom_domains
, I get this error:
-----> Adding custom_domains to uplate... failed
! Please verify your account to install this add-on
! For more information, see http://devcenter.heroku.com/categories/billing
! Confirm now at https://heroku.com/confirm
Also, when I click on any "Verify" link on the website (like on the add-on pages), I just get redirected to the same page I was on, but it keeps telling me to verify.
Am I missing something? This is my first app on Heroku so I am still a little confused.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
你当然没有做错什么。确保其新鲜;
我见过类似的报告,有关已验证帐户未显示为已验证的情况 - 这实际上是当客户尝试扩展其测功机时,它一直陷入“验证”查找中,在这种情况下,您最好联系 heroku 支持人员。
You're certainly not doing anything wrong. To make sure it's fresh;
I have seen similar reports of verified accounts not showing as verified - this was actually when a client was trying to scale their dynos and it kept getting stuck in the 'verify' lookp in which case you'll be better off contacting heroku support.
约翰·贝农回答了我原来的问题。然而,我随后收到“您无权访问”。这是因为当我第一次创建应用程序时,我仍然使用另一个帐户的凭据登录。为了解决这个问题,我运行了两个命令:
然后您可以选择运行:
从应用程序中删除旧的电子邮件地址。
John Beynon answered my original question. However, I then was getting the "You do not have access to ". This was because I was still logged in with the credentials from another account when I first created the app. To solve this, I ran two commands:
You can then optionally run:
To remove the old e-mail address from the app.