Can't find config setting 'es_url' (RuntimeError) despite all my research


  • Used Zammad version: v4.1.0
  • Installation method (source, package, …): Source Ubuntu
  • Operating system: Ubuntu 18.04 LTS + Plesk
  • Database + version: MariaDB 10.1.48
  • Elasticsearch version: last
  • Browser + version: Chrome and Firefox

Actual behavior:

*zammad run rails r “Setting.set(‘es_url’, ‘’)”
/opt/zammad/app/models/setting.rb:37:in `set’: Can’t find config setting ‘es_url’ (RuntimeError)

Hello everyone, this is my first question here.
Please excuse my very poor English as well.

Here is my problem.
I have been trying to install Zamad on my dedicated server for several days now, the Ubuntu installation is new and I have also installed Plesk.

I follow the tutorial for the installation by package and I block at the end on the step: run these last commands to complete the setup and configure Zammad to work with Elasticsearch

When I execute the command:

#sudo zammad run rails r “Setting.set(‘es_url’, ‘http://localhost:9200’)”

I get the following error:
sudo zammad run rails r "Setting.set('es_url', 'http://localhost:9200')" /opt/zammad/app/models/setting.rb:37:inset’: Can’t find config setting ‘es_url’ (RuntimeError)
from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/railties- <main>' from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/railties- eval’
from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/railties- perform' from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/thor-1.1.0/lib/thor/command.rb:27:in run’
from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/thor-1.1.0/lib/thor/invocation.rb:127:in invoke_command' from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/thor-1.1.0/lib/thor.rb:392:in dispatch’
from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/railties- perform' from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/railties- invoke’
from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/railties- <main>' from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in require’
from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in block in require_with_bootsnap_lfi' from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/loaded_features_index.rb:65:in register’
from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in require_with_bootsnap_lfi' from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in require’
from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/activesupport- block in require' from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/activesupport- load_dependency’
from /opt/zammad/vendor/bundle/ruby/2.6.0/gems/activesupport- require' from /opt/zammad/bin/rails:9:in

I have tried all the solutions I find on Google and I can’t seem to resolve this difficulty.
I am new to this field.

Thank you all for your help

I don’t know which tutorial you used, but please consider to use our documentation:

Please also note that the source code installation is -by far- the most difficult installation type and may not suitable for your knowledge. Please don’t take this personal, I’m trying to save you from sleepless nights.

It seems like you didn’t complete the initialization of the database successfully:

As you chose to stick to MySQL installation this is probably the root of your issues.
It’s hard to help you at this state because you may have encountered error messages before above onces appeared without noticing.

Please repeat the installation process - you should consider your current installation as broken.
You may want to use the docker or package installation instead.

Another sidemark:
Installing Zammad on a server that has much more other tasks to do and even runs a management software like Plesk or similar may be a bad idea. Zammad is ressource hungry, system performance may suffer under that decision. Apart from Plesk potentially shooting your knees because you’re trying something it’s probably not made for.

I verified our documentation steps to ensure it’s not faulty. Except for the uncompress step there were no issues.

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.