You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
As part of the recent syslog changes (#354), changes were made to install.py that drop opensearch access which previously defaulted to available for localhost (docker-compose.yaml would have 127.0.0.1:9200:9200 for nginx-proxy service. Not sure if this was intentional or not, but it only survives now if you want to expose to external network.
To Reproduce
Steps to reproduce the behavior:
install picking defaults, and 9200 is not accessible: $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 37f1e3e17fdd apcon/malcolm/nginx-proxy:25.01.0 "/sbin/tini -- /usr/…" About an hour ago Up 14 minutes (healthy) 0.0.0.0:443->443/tcp malcolm-nginx-proxy-1
Expected behavior
Expect that previous accessibility would be available: $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 0a355e3577de apcon/malcolm/nginx-proxy:24.12.0 "/sbin/tini -- /usr/…" 28 hours ago Up 28 hours (healthy) 0.0.0.0:443->443/tcp, 127.0.0.1:9200->9200/tcp malcolm-nginx-proxy-1
**Screenshots and/or Logs **
If applicable, attach screenshots or container logs (e.g., the relevant bits of ./scripts/logs) to help explain your problem.
Locking that down was an intentional change, but maybe we should make it an option during configuration. Thanks for letting us know this affected a use case. Of course, as I'm sure you know, in the meantime while we consider it you may add 127.0.0.1:9200:9200 into the ports section for opensearch service in your docker-compose.yml to restore the previous behavior.
Describe the bug
As part of the recent syslog changes (#354), changes were made to install.py that drop opensearch access which previously defaulted to available for localhost (docker-compose.yaml would have 127.0.0.1:9200:9200 for nginx-proxy service. Not sure if this was intentional or not, but it only survives now if you want to expose to external network.
To Reproduce
Steps to reproduce the behavior:
$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 37f1e3e17fdd apcon/malcolm/nginx-proxy:25.01.0 "/sbin/tini -- /usr/…" About an hour ago Up 14 minutes (healthy) 0.0.0.0:443->443/tcp malcolm-nginx-proxy-1
Expected behavior
Expect that previous accessibility would be available:
$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 0a355e3577de apcon/malcolm/nginx-proxy:24.12.0 "/sbin/tini -- /usr/…" 28 hours ago Up 28 hours (healthy) 0.0.0.0:443->443/tcp, 127.0.0.1:9200->9200/tcp malcolm-nginx-proxy-1
**Screenshots and/or Logs **
If applicable, attach screenshots or container logs (e.g., the relevant bits of
./scripts/logs
) to help explain your problem.Malcolm Version:
How are you running Malcolm?
Additional context
I suggest basically reverting this part of commit https://github.com/cisagov/Malcolm/commit/02cf852b9ebe9d29f1570485ddc06ffcd39050bc as following:
instead of:
The text was updated successfully, but these errors were encountered: