Cannot list cluster IDs for export_monitoring.sh

When trying to list the cluster_uuids, to be able to choose the correct one to export, we are faced with an unexpected exception, indicating that we should enter the cluster_uuid:

```
support-diagnostics-8.1.2$ ./export-monitoring.sh -u elastic -p -h myhost --port 9243 --noVerify --bypassDiagVerify --list
Using /usr/bin/java as Java Runtime
Using -Xms256m -Xmx2000m for options.
2021-01-13 12:59:09,288 main ERROR Unable to locate appender "diag" for logger config "root"
Processing diagnosticInputs...
Elasticsearch user password: ********************************
Deleted directory: /path/to/diagnostics/support-diagnostics-8.1.2/monitoring-export.
Diagnostic logger reconfigured for inclusion into archive
Entered cluster id not found - unexpected exception. Please enure you have a valid cluster_uuid for the monitored clusters. Check diagnostics.log for more details.
Cannot contiue processing. Exiting Check diagnostics.log in the archive file for more detail.
Closing loggers.
Archiving diagnostic results.
Archive: /path/to/diagnostics/support-diagnostics-8.1.2/monitoring-export-20210113-125913.zip was created
Deleted directory: /path/to/diagnostics/support-diagnostics-8.1.2/monitoring-export.
support-diagnostics-8.1.2$ ./export-monitoring.sh -u elastic -p -h myhost --port 9243 --noVerify --bypassDiagVerify --list
Using /usr/bin/java as Java Runtime
Using -Xms256m -Xmx2000m for options.
2021-01-13 13:00:14,343 main ERROR Unable to locate appender "diag" for logger config "root"
Processing diagnosticInputs...
Elasticsearch user password: ************************
Deleted directory: /path/to/diagnostics/support-diagnostics-8.1.2/monitoring-export.
Diagnostic logger reconfigured for inclusion into archive
Entered cluster id not found - unexpected exception. Please enure you have a valid cluster_uuid for the monitored clusters. Check diagnostics.log for more details.
Cannot contiue processing. Exiting Check diagnostics.log in the archive file for more detail.
Closing loggers.
Archiving diagnostic results.
Archive: /path/to/diagnostics/support-diagnostics-8.1.2/monitoring-export-20210113-130018.zip was created
Deleted directory: /path/to/diagnostics/support-diagnostics-8.1.2/monitoring-export.
support-diagnostics-8.1.2$ ls -lrt
total 64
-rwxr-xr-x 1 myuser myuser 86 Feb 18 2020 docker-build.sh
-rwxr-xr-x 1 myuser myuser 994 May 19 2020 import-monitoring.sh
-rwxr-xr-x 1 myuser myuser 994 May 19 2020 export-monitoring.sh
-rw-r--r-- 1 myuser myuser 892 May 19 2020 export-monitoring.bat
-rwxr-xr-x 1 myuser myuser 984 May 19 2020 diagnostics.sh
-rw-r--r-- 1 myuser myuser 884 May 19 2020 diagnostics.bat
-rwxr-xr-x 1 myuser myuser 962 Jun 4 2020 scrub.sh
-rw-r--r-- 1 myuser myuser 876 Jun 4 2020 scrub.bat
-rw-r--r-- 1 myuser myuser 892 Jun 4 2020 import-monitoring.bat
drwxr-xr-x 1 myuser myuser 4096 Jul 28 09:26 lib
drwxr-xr-x 1 myuser myuser 4096 Jul 28 09:26 docker
drwxrwxrwx 1 myuser myuser 4096 Dec 16 14:43 20201216-1
drwxrwxrwx 1 myuser myuser 4096 Jan 13 12:54 monitoring-export-20210113-125422
drwxr-xr-x 1 myuser myuser 4096 Jan 13 13:37 config
-rw-rw-rw- 1 myuser myuser 757 Jan 13 13:42 monitoring-export-20210113-124257.zip
-rw-rw-rw- 1 myuser myuser 754 Jan 13 13:43 monitoring-export-20210113-124325.zip
-rw-rw-rw- 1 myuser myuser 757 Jan 13 13:45 monitoring-export-20210113-124503.zip
-rw-rw-rw- 1 myuser myuser 757 Jan 13 13:48 monitoring-export-20210113-124810.zip
-rw-rw-rw- 1 myuser myuser 772 Jan 13 13:54 monitoring-export-20210113-125422.zip
-rw-rw-rw- 1 myuser myuser 757 Jan 13 13:57 monitoring-export-20210113-125752.zip
-rw-rw-rw- 1 myuser myuser 760 Jan 13 13:59 monitoring-export-20210113-125913.zip
-rw-rw-rw- 1 myuser myuser 0 Jan 13 14:00 startup.log
-rw-rw-rw- 1 myuser myuser 756 Jan 13 14:00 monitoring-export-20210113-130018.zip
support-diagnostics-8.1.2$ unzip monitoring-export-20210113-130018.zip
Archive: monitoring-export-20210113-130018.zip
warning: stripped absolute path spec from /monitoring-export-20210113-130018/
creating: monitoring-export-20210113-130018/
warning: stripped absolute path spec from /monitoring-export-20210113-130018/extract.log
inflating: monitoring-export-20210113-130018/extract.log
support-diagnostics-8.1.2$ cat monitoring-export-20210113-130018.zip
cat: write error: Input/output error
support-diagnostics-8.1.2$ cat monitoring-export-20210113-130018/extract.log
13:00:17.393 [main] INFO com.elastic.support.BaseService - Diagnostic logger reconfigured for inclusion into archive
13:00:18.932 [main] INFO com.elastic.support.monitoring.MonitoringExportService - Entered cluster id not found - unexpected exception. Please enure you have a valid cluster_uuid for the monitored clusters. Check diagnostics.log for more details.
13:00:18.936 [main] ERROR com.elastic.support.monitoring.MonitoringExportService - com.elastic.support.diagnostics.DiagnosticException: Could not retrieve the Elasticsearch version - unable to continue. Status: 400 Reason: Bad Request. Rejected
13:00:18.938 [main] ERROR com.elastic.support.monitoring.MonitoringExportService - Cannot contiue processing. Exiting Check diagnostics.log in the archive file for more detail.
13:00:18.978 [main] INFO com.elastic.support.BaseService - Closing loggers.
13:00:18.980 [main] INFO com.elastic.support.BaseService - Archiving diagnostic results.
support-diagnostics-8.1.2$ curl -k -u elastic https://myhost:9243
Enter host password for user 'elastic':
{
"name" : "instance-0000000035",
"cluster_name" : "mycluster",
"cluster_uuid" : "myuuid",
"version" : {
"number" : "7.9.1",
"build_flavor" : "default",
"build_type" : "docker",
"build_hash" : "083627f112ba94dffc1232e8b42b73492789ef91",
"build_date" : "2020-09-01T21:22:21.964974Z",
"build_snapshot" : false,
"lucene_version" : "8.6.2",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}
support-diagnostics-8.1.2$
```
We have also tried the interactive script, but this yields the same results. We suspected that maybe the credentials are not correct, or there is some proxy etc. between, but a simple cURL shows that connection is possible from this machine with the same credentials.