The below morpheus.rb option that can be switched from false to true.
elasticsearch['secure_mode'] = false
However, we don’t recommend configuring this setting in All-in-One and HA environments as we haven’t documented the manual steps for configuring TLS on nodes two and three. But that’s just a warning and you can totally ignore that.
Is elasticsearch[‘secure_mode’] recommended/supported on a single-node installation?
Reason I ask, when I enabled this setting on a Morpheus v 5.4.15 installation, morpheus-ctl bombed with the following error:
execute the ruby block elasticsearch_wait
execute[update elastic user password] action run
================================================================================
Error executing action run on resource ‘execute[update elastic user password]’
Mixlib::ShellOut::ShellCommandFailed
Command execution failed. STDOUT/STDERR suppressed for sensitive resource
[2023-03-15T13:37:15+00:00] INFO: Running queued delayed notifications before re-raising exception
Running handlers:
[2023-03-15T13:37:15+00:00] ERROR: Running exception handlers
Running handlers complete
[2023-03-15T13:37:15+00:00] ERROR: Exception handlers complete
Chef Client failed. 17 resources updated in 26 seconds
[2023-03-15T13:37:15+00:00] FATAL: Stacktrace dumped to /opt/morpheus/embedded/cookbooks/cache/chef-stacktrace.out
[2023-03-15T13:37:15+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2023-03-15T13:37:15+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[update elastic user password] (morpheus-solo::elasticsearch line 385) had an error: Mixlib::ShellOut::ShellCommandFailed: Command execution failed. STDOUT/STDERR suppressed for sensitive resource