Our Brands

Welcome to the Schneider Electric Website

Welcome to our website.
		
How can we help you today?
PowerChute Network Shutdown v5 reports "Could not connect to Host over the network."

Article available in these languages: Japanese

Issue:
PowerChute Network Shutdown v5 reports "Could not connect to Host over the network." when configuring with VMware ESXi 8 host.

Could not connect to Host

Product:
PowerChute Network Shutdown version 5

Environment:
VMware ESXi 7 or 8 host that VMware vCenter Server does not manage.

Cause:
Security certificate created with the CN= localhost.localdomain
During the installation of ESXi, the installer generates a self-signed certificate for each ESXi host, but the process is performed before the ESXi identity is configured. This means all ESXi hosts have a common name in their self-signed certificate of localhost.localdomain.



Security Certificate
Solution:
1 - Verify that the ESXi host IP address and/or domain name have been entered correctly.
2 - Verify the ESXi host can be pinged from the PowerChute VM or server PowerChute is running on.
3 - Review the security certificate presented by the host. It should contain the host IP address or domain name as the CN.

If the CN = localhost.localdomain, create a new security certificate after adding the correct domain name to the host.


To generate a self-signed certificate

1 - Login to the ESXi host over SSH
a. Requires ESXi shell and SSH access to be enabled on the host

2 - Back up the existing certificate files

a. mv /etc/vmware/ssl/rui.crt /etc/vmware/ssl/rui.crt.old
b. mv /etc/vmware/ssl/rui.key /etc/vmware/ssl/rui.key.old
3 - Generate a new certificate that contains the FQDN for the CN value.
a. /sbin/generate-certificates
4 - Restart the hostd service on the host
a. /etc/init.d/hostd restart

5 - Login to the PowerChute VM
a. Edit /etc/hosts file and add the IP address and hostname of the ESXi host
Examples: 192.168.0.100 ESXiHost100.homelab.local or 192.168.0.100 ESXi100 if DNS is not configured.
For help with editing the hosts file, please see How to edit the hosts file on the system PowerChute Network Shutdown has been installed on to.

6 - Reboot the PowerChute VM
a. The command is init 6

7 - Login to the PowerChute web interface
a. Run the setup wizard

Schneider Electric Malaysia

PowerChute Network Shutdown v5 reports "Could not connect to Host over the network."

Article available in these languages: Japanese

Issue:
PowerChute Network Shutdown v5 reports "Could not connect to Host over the network." when configuring with VMware ESXi 8 host.

Could not connect to Host

Product:
PowerChute Network Shutdown version 5

Environment:
VMware ESXi 7 or 8 host that VMware vCenter Server does not manage. 

Cause:
Security certificate created with the CN= localhost.localdomain
During the installation of ESXi, the installer generates a self-signed certificate for each ESXi host, but the process is performed before the ESXi identity is configured. This means all ESXi hosts have a common name in their self-signed certificate of localhost.localdomain.



Security Certificate
Solution:
1 - Verify that the ESXi host IP address and/or domain name have been entered correctly.
2 - Verify the ESXi host can be pinged from the PowerChute VM or server PowerChute is running on.
3 - Review the security certificate presented by the host. It should contain the host IP address or domain name as the CN.

If the CN = localhost.localdomain, create a new security certificate after adding the correct domain name to the host.


To generate a self-signed certificate

1 - Login to the ESXi host over SSH
            a. Requires ESXi shell and SSH access to be enabled on the host

2 - Back up the existing certificate files

a. mv /etc/vmware/ssl/rui.crt /etc/vmware/ssl/rui.crt.old
b. mv /etc/vmware/ssl/rui.key /etc/vmware/ssl/rui.key.old
3 - Generate a new certificate that contains the FQDN for the CN value.
           a. /sbin/generate-certificates
4 - Restart the hostd service on the host
          a. /etc/init.d/hostd restart

5 - Login to the PowerChute VM
           a. Edit /etc/hosts file and add the IP address and hostname of the ESXi host
Examples: 192.168.0.100 ESXiHost100.homelab.local or 192.168.0.100 ESXi100 if DNS is not configured. 
For help with editing the hosts file, please see How to edit the hosts file on the system PowerChute Network Shutdown has been installed on to.

6 - Reboot the PowerChute VM
           a. The command is init 6

7 - Login to the PowerChute web interface 
           a. Run the setup wizard

 

Schneider Electric Malaysia

Explore more
Range:
Explore more
Range:
Users group

Discuss this topic with experts

Visit our Community for first-hand insights from experts and peers on this topic and more.
Users group

Discuss this topic with experts

Visit our Community for first-hand insights from experts and peers on this topic and more.
Explore more
Range:
Explore more
Range:

Need help?

  • Start here!

    Find answers now. Search for a solution on your own, or connect with one of our experts.

  • Contact Support

    Reach out to our customer care team to receive more information, technical support, assistance with complaints and more.

  • Where to buy?

    Easily find the nearest Schneider Electric distributor in your location.

  • Search FAQs

    Search topic-related frequently asked questions to find answers you need.

  • Contact Sales

    Start your sales enquiry online and an expert will connect with you.

I'd like to receive news and commercial info from Schneider Electric and its affiliates via electronic communication means such as email, and I agree to the collection of information on the opening and clicks on these emails (using invisible pixels in the images), to measure performance of Schneider Electric's communications and to improve them. For more details, please read our Privacy Policy.

  • Products Documentation
  • Software Downloads
  • Product Selector
  • Product Substitution and Replacement
  • Help and Contact Centre
  • Find our Offices
  • Get a Quote
  • Where to buy
  • Careers
  • Company Profile
  • Report a misconduct
  • Accessibility
  • Newsroom
  • Investors
  • EcoStruxure
  • Job Search
  • Blog
  • Privacy Policy
  • Cookie Notice
  • Terms of use
  • Change your cookie settings
Your browser is out of date and has known security issues.

It also may not display all features of this website or other websites.

Please upgrade your browser to access all of the features of this website.

Latest version for Google Chrome, Mozilla Firefox or Microsoft Edgeis recommended for optimal functionality.