Rustls example won't work with RabbitMQ in Docker

[Relrin]

Hello!

I'm trying to run the following example on my local machine with a RabbitMQ instance. So, the connection URI in my case was slightly changed, to amqps://user:pass@192.168.99.100:5672/?heartbeat=10 instead, but instead of getting a couple of println!, I'm getting the error in a console:

=> cargo run --
   Compiling test-rabbitmq v0.1.0 (file:///Users/valeryisavich/code/test-lapin-rabbitmq)
    Finished dev [unoptimized + debuginfo] target(s) in 4.44 secs
     Running `target/debug/test-lapin-rabbitmq`
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 61, message: "Connection refused" } }', src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Also I'd tried to change the amqps to ampq, but result is the same.
Do you have any ideas how to fix this error, so that it will work?

Docker-compose configuration:

version: "3"

services:
  rabbitmq:
    image: bitnami/rabbitmq:latest
    ports:
      - 5672:5672
      - 15672:15672
    environment:
      - RABBITMQ_USERNAME=user
      - RABBITMQ_PASSWORD=pass

Cargo.toml file in test project:

[package]
name = "test-lapin-rabbitmq"
version = "0.1.0"

[dependencies]
chrono = "0.4.0"
futures = "0.1.17"
lapin-futures = "0.10"
lapin-futures-rustls = "0.10.0"
lapin-futures-tls-api = "0.6.0"
tls-api-stub = "0.1.12"
tokio-core = "0.1.10"
rustls = "0.11.0"
tokio-rustls = "0.4.0"
env_logger = "0.4.3"

[Keruspe]

What domain is your certificate valid for?
You should have this domain pointing to 192.168.99.100 (by adding it in your /etc/hosts for example), and then use this domain in the uri instead of the ip address. We can't validate that the certificate is valid if you aren't using a domain name. I think that's the problem here

[Keruspe]

Also, usually, 5672 is the port for amqp and 5671 for amqps, are you sure 5672 is amqps on this container?

[Relrin]

The bitnami-rabbitmq docker image is using 4369, 5672, 15672 and 25672 TCP ports by default:

=> docker-compose ps
       Name                           Command             State              Ports              
-----------------------------------------------------------------------------------------------
testrabbitmq_rabbitmq_1   /app-entrypoint.sh nami st ...   Up        0.0.0.0:15672->15672/tcp,      
                                                                     25672/tcp, 4369/tcp,           
                                                                     0.0.0.0:5672->5672/tcp 

So, as in docker-compose.yml were mentioned, we have 5672 and 15672 exposed ports for using. The first for connection and the second, 15672 port, is using for getting an access to RabbitMQ management plugin.

[Relrin]

In the current time I'm working without any certificates, therefore I should use amqp in URI instead of amqps. However, as it was mentioned, it's leading to the Connection refuced issue as well.
I will try to replace the actual Docker image on another for a testing purposes, probably on the rabbitmq:latest instead.

[Keruspe]

I think there might be a confusion somewhere. amqps is not something that "magically" happens. If you have a rabbitmq server providing you amqp, connecting to it using amqps just won't work. The rabbitmq server has to be configured for amqps in order to do so.
It like trying to connect to a server using https when it only supports http.

Here, 5672 is the amqp port, and the rabbitmq server behind is listening amqp, not amqps, so when you try to connect using amqps on this port, it basically the same as if you were trying to acccess https://google.com:80/ (try it, it won't work)

[Keruspe]

What happens if you use amqp://user:pass@192.168.99.100:5672/%2F?heartbeat=10

[Relrin]

I've tried to change the URI to the following:

extern crate env_logger;
extern crate futures;
extern crate lapin_futures_rustls;
extern crate tokio_core;

use lapin_futures_rustls::lapin;

use futures::future::Future;
use lapin::channel::ConfirmSelectOptions;
use lapin_futures_rustls::AMQPConnectionRustlsExt;
use tokio_core::reactor::Core;

fn main() {
    env_logger::init().unwrap();

    let mut core = Core::new().unwrap();
    let handle   = core.handle();

    core.run(
        "amqp://user:pass@192.168.99.100:5672/?heartbeat=10".connect(handle, |_| ())
        .and_then(|client| {
            println!("Connected!");
            client.create_confirm_channel(ConfirmSelectOptions::default())
        }).and_then(|channel| {
            println!("Closing channel.");
            channel.close(200, "Bye")
        })
    ).unwrap();
}

But unfortunately receiving the same error:

=> cargo run --
   Compiling test-rabbitmq v0.1.0 (file:///Users/valeryisavich/code/test-rabbitmq)
    Finished dev [unoptimized + debuginfo] target(s) in 4.36 secs
     Running `target/debug/test-rabbitmq`
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 61, message: "Connection refused" } }', src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.

[Keruspe]

Please try with the URI I pasted above, it's slightly different

[Relrin]

The issue didn't dissapear. I still have the same error.

[Keruspe]

Do you have access to the management plugin with these credentials?

[Relrin]

Yes, of course. I can get an access to the management plugin via http://192.168.99.100:15672/ with user as username and pass as password.

[Keruspe]

Could you paste the output with debug logs? like RUST_LOG=debug target/debug/test-rabbitmq?

[Relrin]

Yes, sure. This is an output:

DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 28883 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1207763245945337 }
DEBUG:tokio_core::reactor: consuming notification queue
DEBUG:tokio_core::reactor: adding a new I/O source
DEBUG:tokio_core::reactor: scheduling direction for: 0
DEBUG:tokio_core::reactor: blocking
DEBUG:tokio_core::reactor: added a timeout: 0
DEBUG:tokio_core::reactor: added a timeout: 1
DEBUG:tokio_core::reactor: loop process - 7 events, Duration { secs: 0, nanos: 1063679 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 45630 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1207763247062708 }
DEBUG:tokio_core::reactor: notifying a task handle
DEBUG:tokio_core::reactor: loop process - 1 events, Duration { secs: 0, nanos: 24958 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 29840 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1207763247121140 }
DEBUG:tokio_core::reactor: scheduling direction for: 0
DEBUG:tokio_core::reactor: blocking
DEBUG:tokio_core::reactor: added a timeout: 2
DEBUG:tokio_core::reactor: updating a timeout: 2
DEBUG:tokio_core::reactor: loop process - 1 events, Duration { secs: 0, nanos: 170984 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 6614 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1207763247303173 }
DEBUG:tokio_core::reactor: loop process - 0 events, Duration { secs: 0, nanos: 6909 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 16007250 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1207763263320267 }
DEBUG:tokio_core::reactor: notifying a task handle
DEBUG:tokio_core::reactor: loop process - 1 events, Duration { secs: 0, nanos: 81972 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 55116 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1207763263464715 }
DEBUG:tokio_core::reactor::timeout_token: cancel timeout 2
DEBUG:tokio_core::reactor: cancel a timeout: 2
DEBUG:tokio_core::reactor: scheduling direction for: 0
DEBUG:tokio_core::reactor: blocking
DEBUG:tokio_core::reactor: added a timeout: 2
DEBUG:tokio_core::reactor: loop process - 1 events, Duration { secs: 0, nanos: 654206 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 14525 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1207763264141552 }
DEBUG:tokio_core::reactor: loop process - 1 events, Duration { secs: 0, nanos: 15247 }
DEBUG:tokio_core::reactor: adding a new I/O source
DEBUG:tokio_core::reactor: scheduling direction for: 1
DEBUG:tokio_core::reactor: blocking
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 30599 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1207763264444533 }
DEBUG:tokio_core::reactor: notifying a task handle
DEBUG:tokio_core::reactor: updating a timeout: 2
DEBUG:tokio_core::reactor: scheduling direction for: 0
DEBUG:tokio_core::reactor: blocking
DEBUG:tokio_core::reactor: updating a timeout: 0
DEBUG:tokio_core::reactor: updating a timeout: 1
DEBUG:tokio_core::reactor: loop process - 7 events, Duration { secs: 0, nanos: 158831 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 19239 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1207763264630926 }
DEBUG:tokio_core::reactor: loop process - 1 events, Duration { secs: 0, nanos: 14153 }
DEBUG:tokio_core::reactor: dropping I/O source: 1
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 61, message: "Connection refused" } }', src/libcore/result.rs:906:4
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::_print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::begin_panic
   6: std::panicking::begin_panic_fmt
   7: rust_begin_unwind
   8: core::panicking::panic_fmt
   9: core::result::unwrap_failed
  10: <core::result::Result<T, E>>::unwrap
  11: test_rabbitmq::main
  12: __rust_maybe_catch_panic
  13: std::rt::lang_start
  14: main
DEBUG:tokio_core::reactor::timeout_token: cancel timeout 2
DEBUG:tokio_core::reactor::timeout_token: cancel timeout 0
DEBUG:tokio_core::reactor::timeout_token: cancel timeout 1

[Keruspe]

Ok, I think I know what the problem is, as it happens before lapin even starts to do anything.

Could you try making some hostname point to that ip address and then use the hostname instead of the ip address in the URI?

[Relrin]

At this time I'm getting already an another error, probably related to the URI issues.
Used URI: amqp://user:pass@civic:5672/%2F?heartbeat=10
The management plugin is available via the http://civic:15672/ in my browser with the same credentials.

Debug output:

DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 28818 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1208613770437553 }
DEBUG:tokio_core::reactor: consuming notification queue
DEBUG:tokio_core::reactor: adding a new I/O source
DEBUG:tokio_core::reactor: scheduling direction for: 0
DEBUG:tokio_core::reactor: blocking
DEBUG:tokio_core::reactor: added a timeout: 0
DEBUG:tokio_core::reactor: added a timeout: 1
DEBUG:tokio_core::reactor: loop process - 7 events, Duration { secs: 0, nanos: 773961 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 29253 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1208613771248852 }
DEBUG:tokio_core::reactor: notifying a task handle
DEBUG:tokio_core::reactor: loop process - 1 events, Duration { secs: 0, nanos: 25022 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 20243 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1208613771299383 }
DEBUG:tokio_core::reactor: scheduling direction for: 0
DEBUG:tokio_core::reactor: blocking
DEBUG:tokio_core::reactor: added a timeout: 2
DEBUG:tokio_core::reactor: updating a timeout: 2
DEBUG:tokio_core::reactor: loop process - 1 events, Duration { secs: 0, nanos: 196714 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 8358 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1208613771509103 }
DEBUG:tokio_core::reactor: loop process - 0 events, Duration { secs: 0, nanos: 8068 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 5013258 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1208613776534119 }
DEBUG:tokio_core::reactor: notifying a task handle
DEBUG:tokio_core::reactor: loop process - 1 events, Duration { secs: 0, nanos: 47804 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 17271 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1208613776603294 }
DEBUG:tokio_core::reactor::timeout_token: cancel timeout 2
DEBUG:tokio_core::reactor: cancel a timeout: 2
DEBUG:tokio_core::reactor: scheduling direction for: 0
DEBUG:tokio_core::reactor: blocking
DEBUG:tokio_core::reactor: added a timeout: 2
DEBUG:tokio_core::reactor: loop process - 1 events, Duration { secs: 0, nanos: 370632 }
DEBUG:tokio_core::reactor: loop poll - Duration { secs: 0, nanos: 6638 }
DEBUG:tokio_core::reactor: loop time - Instant { t: 1208613776984361 }
DEBUG:tokio_core::reactor: loop process - 1 events, Duration { secs: 0, nanos: 7998 }
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Custom(Custom { kind: Other, error: InvalidName("civic", "resolv::error::Error::Question") }) }', src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.
DEBUG:tokio_core::reactor::timeout_token: cancel timeout 2
DEBUG:tokio_core::reactor::timeout_token: cancel timeout 0
DEBUG:tokio_core::reactor::timeout_token: cancel timeout 1