[SOLVED] Not able to connect via web interface

U

used1d

Member
Jun 16, 2025
51
2
8
Plaese halp. Complete noob, tryin my damndest, but am hitting brick walls at every turn. Someone said oh ya you can do all that from your own house instead of paying the Gaagle. I'm like, ok just run a few lines of sudo that I copy from forums and I'll be straight. Boyyy was I in for a wild ride! So, finally got v7.4 installed on an old PC, because the latest version (v8.4) was giving me a black screen during installation. Anyway, got v7.4 installed, but I cannot connect to it via web interface. One thing to note is that during installation I did not see that little green dot next to my connection device (which I saw is supposed to show in some videos I watched). Also, I just let the IP and other details on that installation page stay what they showed up as; didn't know what to put so I didn't change them. And so when I type in the IP/8006 the message comes up saying it is taking too long to respond and times out.

No other forums have led me to any sort of solution. I don't know much about coding or networking, so please bare with me.. Not sure what to look for or how to look for it. Needing guidance from the basics to get going. Thanks for any suggestions and help.
 
Last edited:
Hello @used1d , welcome to the forum.

Please answer the following questions:

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
 
Hi @bbgeek17 , thanks for the reply.

  • PVE IP: 192.168.100.2
  • Workstation IP: 192.168.0.2
  • Gateway IP: 192.168.0.1
  • Cannot ping PVE: 4 packets sent, 0 packets received, 4 packets lost
  • SSH into PVE: PuTTY just shows blank black box and times out when SSH into 192.168.100.2 port 22 (tried port 24 also)
  • Output of "ip a" on PVE: <image attached>
  • Workstation output for ipconfig /all ; ip a:
Windows IP Configuration

Host Name . . . . . . . . . . . . : *****
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I219-LM #2
Physical Address. . . . . . . . . : *****
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, June 16, 2025 6:57:04 AM
Lease Expires . . . . . . . . . . : Monday, June 16, 2025 12:02:33 PM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
*****
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wi-Fi 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX200 160MHz
Physical Address. . . . . . . . . : *****
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #6
Physical Address. . . . . . . . . : *****
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 15:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #7
Physical Address. . . . . . . . . : *****
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : *****
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes


Thanks for looking this over. Also, not sure how to set static IP in my router. I read that's what I should be doing too..?
 
Last edited:
used1d said:
  • PVE IP: 192.168.100.2
  • Workstation IP: 192.168.0.2
  • Gateway IP: 192.168.0.1
Click to expand...
As you hopefully already noticed, the IPs of your network nodes belong to different subnets.
While it can be an appropriate configuration, it is most likely not the one for you.
Change the IP of the PVE to match the other nodes on your network (workstation and gateway). For example, 192.168.0.2

You may want to watch a few "network for beginners" videos on youtube as well.



Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: UdoB
@bbgeek17 Thank you for the super basic info haha! I've been trying to mess with subnets to have my networks compartmentalized, but that is becoming even more complicated for me (for now). So, I just changed my PVE IP to a static IP in my main subnet, and matched the gateway IP to that in my main subnet as well. That did the trick after rebooting, of course. Thank you for the advice, I'll continue learning!
 
You must log in or register to reply here.
Top Bottom