Bug? "Could not communicate with the node... from the enrollment token."

I am at this point that I get this error message:

root@AllInOne820redis1v4:/tmp# /usr/share/Elasticsearch/bin/Elasticsearch-reconfigure-node --enrollment-token eyJ2ZXIiOiI4LjIuMCIsImFkciI6WyIxMC4wLjIuMTU6OTIwMCJdLCJmZ3IiOiI3ODgzZjlhZWUyNzNhZGQyMTMzZWMwZDQ5NmViMTlkMzgyZDI5YmQ0YzI3MTc1ZDVkODc4ZDgwN2FlN2QzNzM0Iiwia2V5IjoiZkptWEk0RUJTcVg2X0xJOGQtNGk6QWhJSjhWaUVRYy0wWHdCeUZUMERDdyJ9

This node will be reconfigured to join an existing cluster, using the enrollment token that you provided.
*This operation will overwrite the existing configuration. Specifically: *

    • Security auto configuration will be removed from Elasticsearch.yml*
    • The [certs] config directory will be removed*
    • Security auto configuration related secure settings will be removed from the Elasticsearch.keystore*
      Do you want to continue with the reconfiguration process [y/N]y
      Unable to communicate with the node on https://10.0.2.15:9200/_security/enroll/node. Error was Connection refused
      ERROR: Aborting enrolling to cluster. Could not communicate with the node on any of the addresses from the enrollment token. All of [10.0.2.15:9200] were attempted.

This is logical since it should look at this IP 192.168.56.113 where the second node is running.

QUESTION: Is there a possibility to tell Elasticsearch-reconfigure-node to use a specific IP / network card?

Thanks!!