Ad Widget

Collapse

Unable to change Connections to Proxy Encryption setting in 6.0.4 and 6.0.5

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rbeglinger
    Junior Member
    • Jan 2019
    • 10

    #1

    Unable to change Connections to Proxy Encryption setting in 6.0.4 and 6.0.5

    I've been setting up Zabbix Proxies using Ansible and after we upgraded to 6.0.4, we were unable to setup a new proxy using the zabbix.proxy role with tls_connect configured. I get this error.

    fatal: [localhost -> localhost]: FAILED! => {"changed": false, "msg": "Failed to create proxy dev-zabbix-proxy.dev.internal: ('Error -32602: Invalid params., Invalid parameter "/1/tls_connect": unexpected value "2". while sending {"jsonrpc": "2.0", "method": "proxy.create", "params": {"host": "dev-zabbix-proxy.dev.internal", "status": "5", "tls_connect": "2", "tls_accept": "2", "tls_psk_identity": "PSK : dev-zabbix-proxy.dev.internal", "tls_psk": "*********"}, "auth": "*************", "id": 3}', -32602)"}

    So I went into the WebUI and tried to create an new Proxy and the option to change Connections to proxy is greyed out.

    Click image for larger version

Name:	zabbix_proxy_encryption.png
Views:	726
Size:	12.3 KB
ID:	445594

    I've also checked existing proxies that were configured prior to 6.0.4 and they were configured with Connections to proxy PSK enabled, but I am unable to change that now as the option is greyed out for them as well.

    Click image for larger version

Name:	zabbix_proxy_existing.png
Views:	598
Size:	14.3 KB
ID:	445595

    Is anyone else seeing this issue? I also upgrade to 6.0.5 and the problem remains.

  • Markku
    Senior Member
    Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
    • Sep 2018
    • 1782

    #2
    See the proxy type: if the proxy mode is Active (the default in GUI), then Zabbix server never connects to the proxy, thus the Connections to proxy option is disabled.

    Markku

    Comment

    • rbeglinger
      Junior Member
      • Jan 2019
      • 10

      #3
      Thanks for the reply, they are in fact active proxies. It's just interesting that this just started not working for us. Thanks again.

      Comment

      • Justin417
        Junior Member
        • Feb 2018
        • 13

        #4
        Just in case anyone else ran into this while using the Ansible Zabbix community modules to deploy proxies, I had to remove the:
        HTML Code:
        tls_connect: "PSK"
        parameter from my playbook.

        This allowed my playbooks to run again with Zabbix versions 6.0.4+.

        Comment

        • lptarik
          Member
          • Oct 2021
          • 33

          #5
          I am having same issue with my 5.4 zabbix. Strange

          Comment

          Working...