New to Proxmox fresh install can't access web GUI

DarthKrow13

New Member
Apr 6, 2022
2
0
1
Greetings to all
So I am very new to proxmox I wanted to learn more about VMs so I wanted to use proxmox after watching a few tutorials from CraftComputing and Techno Tim so to better understand to get a feel for proxmox I kept everything to default settings. Everything was successful and my sever rebooted into proxmox and it showed the prompt to log in and the IP address for the web GUI I can log in there (I guess that would mean that is SSH still trying to understand lol), but when I went to use the web part I am getting "This site can’t be reached" "192.168.100.2 took too long to respond." yes I am using https:// and port 8006

I also used the proxmox mobile app and I kept on getting connection timed out

here is a summary of my proxmox install
filesystem ext4
management interface eno1
IP cidr 192.168.100.2/24

any help would be great
from
DarthKrow13
 
What is the IP address of the machine or device you are using to connect? What is the IP address of your router? Are all your devices in the 192.168.100.0/24 subnet?
 
What is the IP address of the machine or device you are using to connect? What is the IP address of your router? Are all your devices in the 192.168.100.0/24 subnet?
Probably not because that 192.168.100.2/24 is the installers default IP that you are supposed to change to a IP/subnet that your router is using.

192.168.100.2/24 means only hosts with IPs bwtween 192.168.100.1 and 192.168.100.255 can connect to your PVE server. So best you install PVE again, choose a valid empty IP (not part of your routers DHCP range, and not already used by another host) of your routers subnet and try it again.
 
Last edited:
Probably not because that 192.168.100.2/24 is the installers default IP that you are supposed to change to a IP/subnet that your router is using.

192.168.100.2/24 means only hosts with IPs bwtween 192.168.100.1 and 192.168.100.255 can connect to your PVE server. So best you install PVE again, choose a valid empty IP (not part of your routers DHCP range, and not already used by another host) of your routers subnet and try it again.
Yea ill try that out first will not be able to get to it till Monday . Untill then I'll just have figure out my ip range that i can use