search

ansible-middleware / amq

A collection to manage AMQ brokers
Apache License 2.0
19 stars 11 forks source link

We cannot access our web console in the latest release of the playbook from external site over https #157

Closed RobertFloor closed 3 months ago

RobertFloor commented 3 months ago
SUMMARY
ISSUE TYPE

We cannot access our web console in the latest release of the playbook from external site over https. This used to work in previous version. We believe this pull request breaks our deployment: https://github.com/ansible-middleware/amq/pull/146/commits/557cd23143e6e833a59468a77cd059f7fbc908ed

We use a bind adrress of 0.0.0.0 in the variable activemq_bind_address. But it seems this pull request changes that to the variable value: "http{{ 's' if activemq_tls_enabled else '' }}://{{ activemq_host }}:{{ activemq_http_port }}". I believe this should be changed to activemq_bind_address?

guidograzioli commented 3 months ago

Are you having a CORS errors? or you just cannot access because the bind is unreacheable from remote?

guidograzioli commented 3 months ago

Reproduced; will revert to activemq_bind_address, and in a future change offer a new parameter to allow to differentiate bind ips for messagging ports and console port