Pass-through Failure When Upgrading from 5.4.3 to 6.5.0

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 5.4.3升级到6.5.0透传失效

| username: magongyong

[TiDB Usage Environment] Production Environment / Testing / Poc

[TiDB Version]

[Reproduction Path] What operations were performed when the issue occurred
Online upgrade of the TiDB cluster from 5.4.3 to 6.5.0, following the official documentation (tiup online upgrade)

[Encountered Issues: Problem Phenomenon and Impact]

  1. HAProxy passthrough failure
  2. For example, the business server IP is, and the HAProxy server is
  3. Before the upgrade, the database account’s whitelist was, and the business server accessed normally
  4. After the upgrade, the business server could not access, and authorization had to be given to the HAProxy server for normal access
  5. Before the upgrade, checking the processlist of the TiDB cluster showed that the host was the business IP, coming from
  6. After the upgrade, after adding authorization to HAProxy, the host field in the processlist was the HAProxy IP
  7. No other additional operations were performed, and the issue was reproducible in different environments when upgrading from 5.4.3 to 6.5.0

[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

| username: tidb菜鸟一只 | Original post link

To configure HAProxy to pass through IP, you mainly need to configure the send-proxy option in the HAProxy configuration file and set the TiDB configuration proxy-protocol.networks to the IP of the machine where HAProxy is located.
Have you configured both of these?

| username: magongyong | Original post link

These two are definitely there, they haven’t changed before.

| username: tidb菜鸟一只 | Original post link

tiup cluster edit-config

Check the current value of the proxy-protocol.networks parameter in TiDB to see if there are any issues after the upgrade.

| username: magongyong | Original post link

No change

| username: magongyong | Original post link

Brother, how’s the upgrade effect on your side? Haven’t encountered this problem, right?

| username: magongyong | Original post link

I am planning to upgrade the HAProxy version. The current version is 1.5.18, and the production version is 1.8.10. I will upgrade to version 2.2 or later and then take a look.

| username: chenhanneu | Original post link

Bug, it will be fixed in version 6.5.1.

| username: tidb菜鸟一只 | Original post link

It is indeed a bug.

| username: magongyong | Original post link

Okay, thank you.

| username: system | Original post link

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