Uploaded image for project: 'MariaDB Connector/C'
  1. MariaDB Connector/C
  2. CONC-783

When proxy_protocol is misconfigured, MaxScale (via Connector/C) doesn't always log the error properly

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 3.3, 3.4
    • 3.4.7, 3.3.17
    • Protocol
    • None

    Description

      When proxy_protocol is enabled in MaxScale, but MariaDB is not configured to allow proxy connections from the incoming MariaDB IP in proxy_protocol_networks, MaxScale can log a generic connection error and not that proxy protocol is the issue. This causes delay in troubleshooting and general confusion.

      Expected:

      2025-07-21 08:47:26   error  : Monitor was unable to connect to server server2[10.115.0.32:3306] : 'Proxy header is not accepted from 10.115.0.30'
      

      Problematic log entry:

      error  : Monitor was unable to connect to server server2[10.115.0.32:3306] : 'Lost connection to server at 'sending authentication information', system error: 32'
      

      Attachments

        Issue Links

          Activity

            People

              wlad Vladislav Vaintroub
              Ali.maria Alasdair Haswell
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.