Unable to download RabbitMQ plugins from Bintray

[Tõnis Kasekamp]

I'm trying to download a the rabbitmq_delayed_message_exchange plugin from Bintray, but the response I get is 403 Forbidden. I tried with other RabbitMQ plugins from Bintray and get the same error. 

Resources from other publishers download just fine.

Anyone know anything about this? Is there an alternative source for this plugin?

[Jean-Sébastien Pédron]

On 08.08.2017 13:41, Tõnis Kasekamp wrote:
> I'm trying to download a the rabbitmq_delayed_message_exchange plugin
> from Bintray

> <https://dl.bintray.com/rabbitmq/community-plugins/rabbitmq_delayed_message_exchange-0.0.1.ez>,

> but the response I get is 403 Forbidden.

Hi!

Yes, I confirm this, it is the same for us. We are talking to our IT to
solve this issue. Sorry for the breakage...

> Is there an alternative source for this plugin?

Unfortunately, no :(

You could try to clone the `stable` branch and build it on a Unix host
with GNU Make and Erlang installed:

git clone -b stable \
https://github.com/rabbitmq/rabbitmq-delayed-message-exchange.git
make
make dist

--
Jean-Sébastien Pédron
Pivotal / RabbitMQ

[Tõnis Kasekamp]

Thanks for the reply!

Do you estimate it will be solved within hours or days?

[Jean-Sébastien Pédron]

On 08.08.2017 14:31, Tõnis Kasekamp wrote:
> Do you estimate it will be solved within hours or days?

I hope within hours but we can't promise anything :(

[Michael Klishin]

We've contacted JFrog (Bintray) support about this. We will update this thread as the

situation develops.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send an email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Matthew Ceroni]

This issue is happening again. Is this being investigated? 

On Tuesday, August 8, 2017 at 5:50:53 AM UTC-7, Michael Klishin wrote:

We've contacted JFrog (Bintray) support about this. We will update this thread as the

situation develops.

On Tue, Aug 8, 2017 at 3:32 PM, Jean-Sébastien Pédron <jean-se...@rabbitmq.com> wrote:

On 08.08.2017 14:31, Tõnis Kasekamp wrote:
> Do you estimate it will be solved within hours or days?

I hope within hours but we can't promise anything :(

--
Jean-Sébastien Pédron
Pivotal / RabbitMQ

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send an email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Michael Klishin]

It has been reported to Bintray support.

We apologize for the issues it creates for your deployments but please understand that Bintray provides no warnings whatsoever to open source plan users when they surpass a certain quota (such as storage). They just block and ask to contact support.

To post to this group, send email to rabbitm...@googlegroups.com.

[pawlica....@gmail.com]

Hello, there seems to be again same issue with Bintray. I woulike to use yum repository to download all necessary files for latest rabbitmq release, but every attempt to use Bintray has failed. How can I obtain latest rabbitmq with no struggle with dependencies? :o) Thanks

Dne středa 24. ledna 2018 20:40:24 UTC+1 Michael Klishin napsal(a):

[pawlica....@gmail.com]

OK, I have get it from packagecloud, but still faulty repository creates confusion. It might be beneficial to switch to more reliable primary repository :o)

Dne neděle 30. září 2018 15:30:23 UTC+2 pawlica....@gmail.com napsal(a):

[Michael Klishin]

It's a not a reliability problem. Bintray blocks orgs that go above a certain storage or download quota without any explanation

and doesn't let organizations monitor their quota or otherwise understand why they were blocked.

We've been trying to convince Bintray (JFrog) to at least add monitoring for over 6 months, so far to no avail.

We've contacted their support again.

[Michael Klishin]

We've removed all download links that point to Bintray in favor of GitHub, which never rate limits (that I know of).

We will move community plugin builds to GitHub next week. Package Cloud already can serve as a Bintray

alternative for Debian/apt and RPM/yum repositories [1]. There are things that we don't publish to PC at the moment

(e.g. Debian packages of Erlang/OTP). That might take longer to resolve than direct downloads but it will be done one day.

1. https://packagecloud.io/rabbitmq

[Michael Klishin]

Our repo has been unblocked. We are trying to find out why it was blocked this time around

and how we can monitor this.

[Guillaume Rossolini]

Hi Michael,

Thank you, the instructions to get RabbitMQ from PackageCloud worked (apt debian), but there doesn't seem to be the same for erlang yet? Unless I've missed them.

Also, on Stretch apt displays the following when using Bintray as a source:

E: The repository 'http://dl.bintray.com/rabbitmq/debian stretch Release' is no longer signed.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration details.

Regards,

[Michael Klishin]

Erlang packages are not currently distributed via Package Cloud. They will be when we get to it.

The policy of anything we put on Bintray from now on is "it must be also available from an alternative location" since

our org is hitting all kinds of Bintray limits and Bintray doesn't allow open source accounts to monitor those limits.

I will post something about our plans on future Bintray usage in a separate thread later today.

[dom...@gmail.com]

Can confirm that packages are currently not signed on bintray. I got this issue since about one week.

[Michael Klishin]

This thread is about community plugins and Bintray blocking our org, not signing.

Our pipeline is not responsible for package indexing (which involves creation of the signature file), Bintray is. We'll investigate

what's going on and as soon as our pipeline can produce package revisions, publish a revision of 3.6.16 and 3.7.8 in hopes it will

force re-indexing and the signatures file will be produced.

Might be worth filing a support ticket with Bintray as well but I fully expect that they'd recommend a revision republishing anyway.

[dom...@gmail.com]

packages are now signed again on bintray.

[Michael Klishin]

It must be the moon phase.