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
On all other places where I have put IPv6 address in Zabbix configs (DB_SERVER_HOST, or ZBX_SERVER_HOST in proxies) the IPv6 address can be written without brackets.
Only in the frontend this does not work (and even there DB_SERVER_HOST works without brackets which is confusing).
I would expect the writing style of IPv6 addresses to be cosistent. Or is there is a reason why only in this place brackets are mandatory?
ACTUAL RESULTS
When ZBX_SERVER_HOST is configured with IPv6 without brackets and you reload the Zabbix GUI there is no attempt to reach the Zabbix server. I checked this with tcpdump.
The text was updated successfully, but these errors were encountered:
After I noticed that I have to use the brackets for ZBX_SERVER_HOST I tested what happens when I also write the address for DB_SERVER_HOST in brackets. But this does not work. You can see above three combinations I have tested.
You have to use ZBX_SERVER_HOST with brackets but DB_SERVER_HOST without brackets. I find this not very intuitive.
SUMMARY
On all other places where I have put IPv6 address in Zabbix configs (DB_SERVER_HOST, or ZBX_SERVER_HOST in proxies) the IPv6 address can be written without brackets.
Only in the frontend this does not work (and even there DB_SERVER_HOST works without brackets which is confusing).
OS / ENVIRONMENT / Used docker-compose files
OS: CentOS Stream release 9
Docker image: zabbix/zabbix-web-nginx-pgsql:alpine-7.0.5
CONFIGURATION
STEPS TO REPRODUCE
This does not work:
This does not work:
Using brackets with DB_SERVER_HOST gives this error:
This works:
EXPECTED RESULTS
I would expect the writing style of IPv6 addresses to be cosistent. Or is there is a reason why only in this place brackets are mandatory?
ACTUAL RESULTS
When ZBX_SERVER_HOST is configured with IPv6 without brackets and you reload the Zabbix GUI there is no attempt to reach the Zabbix server. I checked this with tcpdump.
The text was updated successfully, but these errors were encountered: