-
Notifications
You must be signed in to change notification settings - Fork 33
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
can't get grinbox to start #15
Comments
Hi @cgilliard, latest grinbox code uses stomp protocol to connect to rabbit. Please make sure you are running the rabbitmq stomp plugin (https://www.rabbitmq.com/stomp.html) and you use the correct port to connect to it from Let me know if you need more help - might be easier to chat over keybase. Cheers, |
Thanks. This did resolve it, but now I'm trying to get the wallet713
instances to communicate and I see that grinbox is listening on 13420 for
HTTP connections, so i assumed I should change DEFAULT_GRINBOX_PORT to
13420 in wallet713 if I wanted to communicate with this instance. But when
I make that change, I get the following displayed on grinbox:
[2019-04-27T19:54:56Z *ERROR* grinbox::server] the server encountered an
error: WS Error <Http(Token)>: Invalid byte where token is required.
Where do I find you on keybase?
…On Sat, Apr 27, 2019 at 12:44 AM ravidio ***@***.***> wrote:
Hi @cgilliard <https://github.com/cgilliard>, latest grinbox code uses
stomp protocol to connect to rabbit. Please make sure you are running the
rabbitmq stomp plugin (https://www.rabbitmq.com/stomp.html) and you use
the correct port to connect to it from
Let me know if you need more help - might be easier to chat over keybase.
Cheers,
Ravid
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABXFVN66QN77WRU7MBNHSILPSP75RANCNFSM4HI3TRMA>
.
|
Nice! I’m “ravidio” on keybase. By default wallet713 communicates with grinbox over wss so you’d need a domain and cert. you could add grinbox_protocol_unsecure=true in wallet713 if you want to use ws and then it should work on 13420. |
Update from Bugreport: vault713#15
No matter what I set username/password to I always get:
[2019-04-27T06:49:19Z ERROR grinbox::broker::rabbit_broker] broker thread ending!
and process halts.
I have installed a rabbitmq and ensured it's running and has a user name rabbit with password guest. I even println the user name, password, and address and they match what I configured in rabbitmq with the following command:
rabbitmqctl change_password rabbit guest
Any ideas would be appreciated. More detailed failure messages would also be very helpful.
The text was updated successfully, but these errors were encountered: