After reboot machine can't access to web interface

[lab10]

Hi,

i have made reboot for my local machine (PC) after that run VM proxmox but when try to enter web interface can not it's show time out connection ?

how can to solve this issue ?

thanks

 

[bbgeek17]

Hi @lab10, welcome to the forum.

Sounds like you need to invest some time in troubleshooting. Collecting this information may give you enough details to get on the right track:

• What is the IP of the PVE server?
• What is the IP of your workstation?
• What is the IP of your gateway?
• Can you ping the PVE server?
• Can you ssh into PVE server?
• What is the output of "ip a" on PVE?
• What is the corresponding output from your workstation? (ipconfig /all ; ip a)
• What is the output of "curl -k https://127.0.0.1:8006" when run directly from PVE (over SSH or physical console?)
• What is the output of "curl -k https://LAN_IP:8006" when run directly from PVE (over SSH or physical console?)

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[lab10]

Hello bbgeek17

thanks for youe respons

IP server:
im using

ip a

from termanel in the VMware
172.24.125.132

IP of workstation
How to get ?

IP of gateway
172.24.112.1


Can you ping the PVE server?
No, there is lost packeages


Can you ssh into PVE server?
No


What is the output of "ip a" on PVE?
attahment# 1




What is the corresponding output from your workstation? (ipconfig /all)
Not work, command not found


What is the output of "curl -k https://127.0.0.1:8006" when run directly from PVE (over SSH or physical console?)






What is the output of "curl -k https://LAN_IP:8006" when run directly from PVE (over SSH or physical console?)
could not resolve host: LAN_IP

 

[lab10]

any update ??

thanks

 

[BobhWasatch]

Seriously? He wrote "LAN_IP" to indicate you should substitute the real IP of your server. Do that.

 

[lab10]

pls read carefully,
i was did already curl -k command
if you have answer to my question write instead "Seriously"

 

[BobhWasatch]

It said "could not resolve host LAN_IP". The only way to get that response is to have put, literally, LAN_IP, as the target of the curl command because IP addresses don't need resolving and so can't give that error. You should instead substitute your machine's real IP (e.g 192.168.1.3).

 

[BobhWasatch]

Likewise, he also asked for the IP of the workstation you are trying to browse from. You said "ipconfig /all" did not work. What operating system do you use?

ETA: It appears from what you posted that the PVE web server is running and serving the main page and the Ethernet port is up. That means the issue is almost certainly with the network settings somewhere.

 

[BobhWasatch]

It isn't clear to me, but you seem to be running PVE inside of another virtualization. Is that correct? In that case you need to pay special attention to how the network is set up on the host side. For example, Virtualbox defaults to NAT, which means the host can't access the VM directly but the VM can reach out.

 

[lab10]

Likewise, he also asked for the IP of the workstation you are trying to browse from. You said "ipconfig /all" did not work. What operating system do you use?

ETA: It appears from what you posted that the PVE web server is running and serving the main page and the Ethernet port is up. That means the issue is almost certainly with the network settings somewhere.

Hello BobhWasatch,

ipconfig /all ...... from the VM not work but from the PC it this bellow and my OS Win 11.

Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : DESKTOP-VKRMBR2
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
 
Unknown adapter Local Area Connection:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : TAP-Windows Adapter V9 for OpenVPN Connect
   Physical Address. . . . . . . . . : 00-FF-40-B8-4F-B1
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
 
Ethernet adapter Ethernet 5:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek USB GbE Family Controller
   Physical Address. . . . . . . . . : 00-E0-7A-10-C3-EC
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Unknown adapter HotspotShield Network Adapter:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HotspotShield TAP-Windows Adapter V9
   Physical Address. . . . . . . . . : 00-FF-89-17-EC-69
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Ethernet adapter vEthernet (Work Lab):
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
   Physical Address. . . . . . . . . : 10-7C-61-0C-9B-97
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:1670:18:4656:517c:c3b2:6ee8:7623(Preferred)
   Temporary IPv6 Address. . . . . . : 2001:1670:18:4656:b4bd:2dc7:c6dd:b1eb(Preferred)
   Link-local IPv6 Address . . . . . : fe80::df33:2266:acb9:d35c%8(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.100.2(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : fe80::fa75:88ff:fee6:848a%8
                                       192.168.100.1
   DHCPv6 IAID . . . . . . . . . . . : 487619681
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2E-F0-87-6B-10-7C-61-0C-9B-97
   DNS Servers . . . . . . . . . . . : fe80::1%8
   NetBIOS over Tcpip. . . . . . . . : Enabled
 
Unknown adapter OpenVPN Connect DCO Adapter:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : OpenVPN Data Channel Offload
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Ethernet adapter VMware Network Adapter VMnet1:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
   Physical Address. . . . . . . . . : 00-50-56-C0-00-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::839f:3f1a:7576:20c9%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.17.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 184569942
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2E-F0-87-6B-10-7C-61-0C-9B-97
   NetBIOS over Tcpip. . . . . . . . : Enabled
 
Ethernet adapter VMware Network Adapter VMnet8:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
   Physical Address. . . . . . . . . : 00-50-56-C0-00-08
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d777:90e:6960:3541%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.136.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 201347158
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2E-F0-87-6B-10-7C-61-0C-9B-97
   NetBIOS over Tcpip. . . . . . . . : Enabled
 
Ethernet adapter vEthernet (Default Switch):
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
   Physical Address. . . . . . . . . : 00-15-5D-82-9C-8A
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::c475:3135:9013:ed76%43(Preferred)
   IPv4 Address. . . . . . . . . . . : 172.25.144.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 721425757
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2E-F0-87-6B-10-7C-61-0C-9B-97
   NetBIOS over Tcpip. . . . . . . . : Enabled

and yes the pve inside VMware and the VMware in the OS Win 11

 

[bbgeek17]

There are multiple layers here where things could go wrong. The routing between Windows, ESX, and PVE must be seamless.

The best approach is to have all components on the same subnet/L2. If that's not feasible, you will need to step through each layer methodically.

The issue is likely not with Proxmox, we already proven that services on PVE are working fine.

You might also consider running PVE within "Hyper-V" on the Windows workstation, instead of ESXi.

Good luck!

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[lab10]

i was tried to use Proxmox in Hyper-V and work fine, just in VMware this issue.
so there is chance to solve this ? and how

thanks

 

[BobhWasatch]

The problem is in your VMware configuration. I don't use VMware and so can't help you. Perhaps asking in a VMware forum "how to enable network access from the host to a VM" would be a way to get help.