Shovel connection fails and reports an authentication error

[NishantMunot28]

Describe the bug

while using shovel to move messages from old rabbit (3.10.5) to latest rabbit (3.13.7) getting error authentication failed.
shovellog.txt
I have already checked the username and password and permission on the vhost that are correct.

Reproduction steps

1. Create a rabbitmq with version 3.10.5 add queue and vhost.
2. sample definition provided below to be imported. test.json
   3 . create new rabbitmq with version 3.13.7.
3. import definition.
4. create shovel to migrate message from old rabbitmq queue to new rabbitmq queue

Expected behavior

shovel migration should work, messages to be copied from old to new rabbit

Additional context

No response

[michaelklishin]

@NishantMunot28 please stop filing the same issue over and over again or you will be permanently banned from doing org-wide. What you are "reporting" is not a bug and you are not helping us help you, repeatedly.

We have already answered that in #12108 and we have made it clear that will not troubleshoot authentication problems for you unless you are a paying customer (then file a support ticket) or a regular contributor (which you aren't, I'm afraid).

I have also made sure to update the docs with a few relevant examples of log messages.

We cannot help you with example data such as

2024-08-23 09:48:07.497648+00:00 [error] <0.56338.0>                         [{<<"dest-uri">>,
2024-08-23 09:48:07.497648+00:00 [error] <0.56338.0>                           [{encrypted,
2024-08-23 09:48:07.497648+00:00 [error] <0.56338.0>                                <<"tIFQVXzk4jlRqPzYzoI1RWzM0aKmJeT1gNOKQ4VlvRssxS7711sdl3ggFFs5mtVN6GCU0hU6my9UPAjQ4kFYJmlUo37ZLHdgP2KGDOGaNIbdBQdzxizvaA+8oMJ4/aFAypucR+pOmPuGfC6YQvDyNWONQizNqRJdoDQ2irzWxixAyMD3jweTdkzy7kY2tZeNu9xSUZH7+Zq76Oh+/KDnRvOA=">>}]},
2024-08-23 09:48:07.497648+00:00 [error] <0.56338.0>                          {<<"src-uri">>,
2024-08-23 09:48:07.497648+00:00 [error] <0.56338.0>                           [{encrypted,
2024-08-23 09:48:07.497648+00:00 [error] <0.56338.0>                                <<"+7BePjqsFKauTzJjhLaFMWbewR1gPqlvis2zY5/KK9XkhPuqAeKUSaNi4agcMpHQpaKlEKTrvVIUOfDyOb0rGJKav/Yln2bh9M/GXYLkoVEPBLDrQXTsUnLm+P4HGxqDPG0sRh4boaxsoc4YHnaj9gp+mOkDr4n2S0QK6hNaiy8fNOFn">>}]},

anyway. Please put together an executable way to reproduce or seek help elsewhere.

This message is very specific:

2024-08-23 09:48:07.485555+00:00 [debug] <0.71701.0> Shovel 'user-test-28-shovel' connected to source
2024-08-23 09:48:07.496213+00:00 [error] <0.71701.0> Shovel 'user-test-28-shovel' failed to connect (URI: amqp://CONTEXT.DOMAIN_URL:5672/xxxx): ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
2024-08-23 09:48:07.496329+00:00 [error] <0.71701.0> Shovel 'user-test-28-shovel' has no more URIs to try for connection
2024-08-23 09:48:07.496442+00:00 [error] <0.71701.0> Shovel 'user-test-28-shovel' could not connect to destination: error failed_to_connect_using_provided_uris

ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile

@NishantMunot28 it even suggests you what to do, see the target node's log files. Where you will very likely discovered one of the messages in the Troubleshooting section.

[michaelklishin]

In addition, if Shovel uses TLS then there is a TLS-specific troubleshooting guide, as well as one on troubleshooting network connectivity.

Use those instructions to narrow the problem down, and see target node's log files (if it is a cluster, the logs fro mall nodes, and if a load-balancer is involved, its logs as well) instead of guessing or repeatedly abusing issues to ask the same question.