brew install ngrok/ngrok/ngrok is not working

[babusureshsaravanan]

I am having below error

==> Fetching downloads for: ngrok/ngrok/ngrok
✘ Cask ngrok (3.37.3)
Error: Download failed on Cask 'ngrok' with message: Download failed: https://bin.ngrok.com/a/5mfSNpNhBZC/ngrok-v3-3.37.3-darwin-arm64.zip
curl: (56) The requested URL returned error: 500

[emastyle]

Here the same

[jpmc]

I also have the "same" issue, but with a 403 instead of a 500.

==> Fetching downloads for: ngrok/ngrok/ngrok
✘ Cask ngrok (3.37.3)
Error: Download failed on Cask 'ngrok' with message: Download failed: https://bin.ngrok.com/a/5mfSNpNhBZC/ngrok-v3-3.37.3-darwin-arm64.zip
curl: (56) The requested URL returned error: 403 

Additionally, trying to go to that link in-browser just to see what happens yields this XML fragment. In case this helps the ngrok folks isolate any logs on their end.

<Error>
  <Code>AccessDenied</Code>
  <Message>Access Denied</Message>
  <RequestId>6F5H71VR4TV8E8PV</RequestId>
  <HostId>du1jqt2ATph88i4cPh49N5ZE6OMqbo24ORBOYkmAFC0QlmSX8YFdsv6r8q9wYe/rz8dvd+bBMgQ=</HostId>
</Error>

[dskecse]

I've run into the same issue with a 403 Forbidden error. And in addition to the info mentioned before, ngrok failed my repo build on Github Actions (under the Annotations section):

Also, I just reproduced the issue locally:

@kmvachhani @zombiezen could you please look into this?

[kaganjd]

ngrok support here- thank you all for the reports.

downloading our latest binary directly from our downloads page (i.e., https://ngrok.com/download/mac-os?tab=download) should work as expected.

we are working as quickly as possible to restore access via homebrew and other distribution channels that do not internally cache our binary. we do now have a status page up at https://status.ngrok.com/ which we'll update as soon as this is fully resolved.

[wayjake]

What a random thing to run into on a Tuesday morning. Someone is checking on the "update google bucket permissions" they just ran 😂

[dskecse]

I can confirm this issue has been resolved. Thanks @kaganjd!