Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rabbitmq-3.9.6 no users/vhost being created #29

Open
Sweatha-g opened this issue Jan 31, 2022 · 4 comments
Open

Rabbitmq-3.9.6 no users/vhost being created #29

Sweatha-g opened this issue Jan 31, 2022 · 4 comments

Comments

@Sweatha-g
Copy link

@cyrilgdn I am using rabbit version 3.9.6 and using latest provider v1.6.0 to create resources and it throws error while creating my vhost and user " Error 405 from RabbitMQ:EOF"

@cyrilgdn
Copy link
Owner

cyrilgdn commented Feb 1, 2022

Hi @Sweatha-g

Could you provide a configuration example of your vhost/user?
Is it on a used cluster or one you are creating?

@deejayprod
Copy link

deejayprod commented Aug 16, 2022

I have the same error.

Terraform version:
Terraform v1.2.3
on windows_amd64

provider 1.6.0

Brand new linux container (rabbitmq:3.10-management-alpine), login with guest user created by default. Rabbitmq runs behind a traefik reverse proxy acting just as an ssl endpoint

vhost declaration:

resource "rabbitmq_vhost" "bla" {
  name = "bla"
}

Error: Error 405 (Error 405 from RabbitMQ: EOF):

******************* EDIT **********************************

-> found the issue, i let a trailing slash (https://myhost/) in the rabbitmq endpoint in the configuration of the provider.... maybe a good idea to sanitize inputs for dummy people like me

@berniedurfee-renaissance

Same issue here using provider v1.8.0 and RabbitMQ 3.12.6.

No trailing slash on the endpoint. :)

I can use curl to create the vhost but when using this provider I get:

Error: Error 405 (Error 405 from RabbitMQ: EOF): 

with rabbitmq_vhost.primary,
  on rabbitmq.tf line 1, in resource "rabbitmq_vhost" "primary":
  1: resource "rabbitmq_vhost" "primary" {

@berniedurfee-renaissance

Found it per this the endpoint URL shouldn't have /api on the end, nor should it have a trailing /.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants