Tidb: Sign in failed: Failed to connect to TiDB in tiup dashboard using current master (0fd81a8) build, but works with release-4.0.5

[fxrcode]

General Question

• login to tiup dashboard.

  • [ ] current master (0fd81a8) build: Sign in failed: Failed to connect to TiDB
  • [x] works with release-4.0.5, and or earlier.

• Screenshot
  

• local envrionment

$ tiup playground --db.binpath ./bin/tidb-server --db 1 --pd 1 --kv 3
Starting component `playground`: /home/fxrc/.tiup/components/playground/v1.1.1/tiup-playground --db.binpath ./bin/tidb-server --db 1 --pd 1 --kv 3
Use the latest stable version: v4.0.5

    Specify version manually:   tiup playground <version>
    The stable version:         tiup playground v4.0.0
    The nightly version:        tiup playground nightly

Playground Bootstrapping...
Start pd instance...
Start tikv instance...
Start tikv instance...
Start tikv instance...
Start tidb instance...
.....
Waiting for tikv 127.0.0.1:20160 ready 
Waiting for tikv 127.0.0.1:20161 ready 
Waiting for tikv 127.0.0.1:20162 ready 
Start tiflash instance...
Waiting for tiflash 127.0.0.1:3930 ready ...
CLUSTER START SUCCESSFULLY, Enjoy it ^-^
To connect TiDB: mysql --host 127.0.0.1 --port 4000 -u root
To view the dashboard: http://127.0.0.1:2379/dashboard
To view the Prometheus: http://127.0.0.1:39675
To view the Grafana: http://127.0.0.1:46245

$ tiup status                                                        
Name     Component   PID      Status   Created Time               Directory                      Binary                                                         Args
----     ---------   ---      ------   ------------               ---------                      ------                                                         ----
S9TWlc4  playground  2044694  RUNNING  2020-09-02T16:08:35-07:00  /home/fxrc/.tiup/data/S9TWlc4  /home/fxrc/.tiup/components/playground/v1.1.1/tiup-playground  --db.binpath ./bin/tidb-server --db 1 --pd 1 --kv 3

• any suggestion how to trace?

[nullnotnil]

I have verified as described. @breeswish PTAL

[ichn-hu]

I encountered this issue yesterday but not realized this is a bug :cry:

[breeswish]

Thanks for the report. Investigating.

[breeswish]

Looks like it is caused by https://github.com/pingcap/tidb/pull/18786 where the advertise IP is always reported as the NIC address while the address may not be listened.

[breeswish]

@djshow832 @crazycs520 PTAL

[crazycs520]

@jyz0309 PTAL

[jyz0309]

get it

[sre-bot]

Integrity check:
severity RCA symptom trigger_condition wa affect_version fix_version fields are empty
@jyz0309
Please comment /info to get template

[ti-srebot]

Please edit this comment to complete the following information

Not a bug

1. Remove the 'type/bug' label
2. Add notes to indicate why it is not a bug

Duplicate bug

1. Add the 'type/duplicate' label
2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: https://github.com/pingcap/tidb/issues/20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

[ti-srebot]

( component or sig(label) FixedVersions AffectedVersions ) fields are empty.