Skip to main content
All CollectionsKnowledge BaseEnterprise WorkloadsTroubleshooting - Enterprise Workloads
Nutanix proxy network settings gives error when doing list network interface via ProxyConf

Nutanix proxy network settings gives error when doing list network interface via ProxyConf

Nutanix proxy network settings gives error when doing list network interface via ProxyConf

Updated over 2 weeks ago

Problem description

While activating the Nutanix proxy via ProxyConf, we encounter an error during the network configuration setup. Specifically, at the 'List Network Interface' step, the following error appears: Failed to list network. Reason: YAML: line - Did not find the expected alphabetic or numeric character.

Cause:

This is typically an issue with the YAML file, as it is space-sensitive. If there are incorrect indentations, extra spaces, or missing colons, the file will fail to parse correctly.

File location of this YAML file is : /etc/netplan/00-installer-config.yaml

Resolution

  • Step 1: Verify the YAML File

    • Run the following command to check the contents of the YAML file:
      ​cat /etc/netplan/00-installer-config.yaml
      If you see the word "any" on line 3, it needs to be corrected.

  • Step 2: Backup the Configuration File

    • Before making any changes, create a backup:
      ​sudo cp /etc/netplan/00-installer-config.yaml /tmp/00-installer-config.yaml.bak

  • Step 3: Adjust File Permissions

    • Ensure the file has the correct permissions:
      ​sudo chmod 600 /etc/netplan/00-installer-config.yaml

  • Step 4: Edit the File

    • Open the file using the Nano editor:

      • sudo nano /etc/netplan/00-installer-config.yaml

    • Locate the line containing "any" and change it to "ens3" (or the appropriate network interface).

    • Save the file by pressing Ctrl + X, then Y, and press Enter.

  • Step 5: Restart the Proxy and Verify

    • Reboot the Nutanix proxy

    • Once the proxy is online, open the ProxyConf utility and try listing the network interfaces again. The error should no longer appear.

Did this answer your question?