-
-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zabbix as default vhost #180
Comments
Hi, So you would like to propose the following change:
This is only for allowing it via an ip instead of an fqdn? Am I correct? |
You can do this already without changing any of the code if you set the following Apache class for your server.
|
This is indeed easier to do, thank you @ju5t . If this work @szemlyanoy would you please let me know? I can update the documentation about this. |
If I set class profile::zabbix::server { then I get obvious duplicate resource error of Class[Apache]. I don't want to set manage_vhost=>false and replicate all params of apache in node definition(or profile) |
You're setting defaults that may be causing issues on existing installations. We don't want Zabbix to be the default for example. You're also missing some documentation on your change. |
ok for me it's absolutely fine to pass default 'false'. |
I'll close this issue as the PR is accepted. |
Hi folks,
Did anyone face with issue when access to zabbix UI by IP address points to default vhost which is effectively just /var/www/ ?
I propose to make change in
apache::vhost { $zabbix_url }
and
apache::vhost { "${zabbix_url}_nonssl"}
resources to add attribute
manage_docroot => false
Tested on my env, I can now access Zabbix by IP.
BR,
Sergey
The text was updated successfully, but these errors were encountered: