How to fix 403 errors from RabbitMQ on Xray [Video]

How to fix 403 errors from RabbitMQ on Xray [Video]

AuthorFullName__c
Loren Yeung
articleNumber
000005064
ft:sourceType
Salesforce
FirstPublishedDate
2021-06-29T19:47:55Z
lastModifiedDate
2021-06-29
VersionNumber
7


Video Transcript:
Hi. My name is Loren from JFrog and today we will be diagnosing, and how to fix a 403 error from rabbitMQ reported by Xray. Here’s an example of what it would look like. In the Xray server log, it says, error connecting to rabbitMQ message queue. Check MQ settings. Exception 403 reason, user or password not allowed. This error is a bit misleading. It generally means that the password was actually incorrect or not provided rather than not allowed. So let’s take a look at a live demo. And so we can see here that Xray has attempted to retry this quite a few times, over a hundred times. You can see it’s continuing to do so. So let’s stop Xray.

Okay. And so the first thing we want to do is to find out if the password has been set for rabbitMQ. So, the easiest way to do this is to find the rabbitMQ conf. So we can locate it via this command. And here it is. We can see here that it has been set. That this parameter, default underscore pass and the password has been set to password. So next, let’s verify that this password is actually correct. So we can do this by using the rabbitMQctl CLI. This would be located here in the op folder. First one, I run a status command. Make sure the RQ is running with the status returns that it’s unavailable or not available. You want to try using the extra user by running SU-Xray first. This is the extralytics user, and sometimes it permissions are owned by this guy, in this user.

Next, let’s verify that the user-password combination is correct. So in this case, the default user is going to be guests. Authenticate. Okay. I can see success. This means that the password is good. Generally the default password will be guests, password or in our case, is supposed to be 2JFXR_rabbitMQ. Now that the rabbitMQ’s accepted it, let’s go verify the system we have on Xray actually has that set. So we can see here that there isn’t a password bill at all. Now let’s start with Xray. We’ll check the service log. And we can see here, all services is actually started. Okay. Just to verify, let’s run a quick curl. Can run netstat to see what the port is on. So we have a customized port here. And there we go, and everything is up and running. Thank you for listening. This has been Loren with JFrog support.