New 3.2 installation, cannot connect via browser

drauku

Renowned Member
Mar 24, 2014
6
0
66
I installed Proxmox VE 3.2 for the first time on my home server hardware today. I first attempted to install via USB key, but that didn't work at all... the installation timed out trying to "unmount cdrom". Well, I went back to the stone-age and burned a CD for the install ISO and it installed correctly, and without issue at all.

I now cannot connect to the Proxmox host via my PC on the local network, but I can ping the host IP address from my PC no problem. Checking ifconfig on the proxmox host, the network adapter is working and has an IP address on the local network (statically assigned, 192.168.1.100). This correctly correlates with my router IP assignment list. Additionally, from the host I am able to ping 4.2.2.2, yahoo.com, and my personal PC on the local network.

Here is the output from ifconfig, transcribed from the proxmox cmd line login on the physical hardware:

Code:
root@proxmox:~$ ifconfig
eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet6 addr: nn##::##n#:##nn:nn##:n#n#/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15902 errors:0 dropped:0 overruns:0 frame:0
TX packets:743 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3105698 (2.9 MiB) TX bytes:51566 (50.3KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 MiB) TX bytes:0 (0.0KiB)


venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::1/64 Scope:Link
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 MiB) TX bytes:0 (0.0KiB)


vmbr0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: nn##::##n#:##nn:nn##:n#n#/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13021 errors:0 dropped:0 overruns:0 frame:0
TX packets:580 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1986783 (1.8 MiB) TX bytes:40908 (39.9KiB)


root@proxmox:~$ ifconfig

All hardware is working fine (I have another HDD I still have XenServer installed on, one with Windows Server 2008r2, and another with a Linux Mint desktop version just for kicks that I used to test the hardware).

Mainboard: Gigabyte A75M-UD2H
AMD Athlon II X4 CPU
16GB memory
2x AOC-SASLP-MV8 SAS Raid Cards

Any insight or help would be appreciated!
 
can you post output of
#hostname
#cat /etc/hosts
#/etc/network/interfaces
Marco

Hope these answer your questions appropriately:

Code:
#root@proxmox:~# hostname
proxmox
#root@proxmox:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.1.100 proxmox.local proxmox pvelocalhost

# The following lines are desirable for IPv6 capable hosts

::1        ip6-localhost ip6-loopback
fe00::0  ip6-localnet
ff00::0  ip6-mcastprefix
ff00::1  ip6-allnodes
ff00::2  ip6-allrouters
ff00::3  ip6-allhosts

root@proxmox:~# /etc/network/interfaces
-bash: /etc/network/interfaces: Permission denied
 
sorry it was
#cat /etc/network/interfaces

Code:
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
  address 192.168.1.100
  netmask 255.255.255.0
  gateway 192.168.1.1
  bridge_ports eth0
  bridge_stp off
  bridge_fd 0

Sorry, I should have caught that myself.
 
Thanks! I got it to work with the https://192.168.1.100:8006

Funny thing, I had tried that before and it didn't work... perhaps when I tested SSH as the first thing it "forced" something to work? I'm not sure....

I am still missing the eth0 in /etc/network/interfaces but who knows if it's a relevant issue or not.

Again, thanks for the help... I just wish when I'd tried that initially it had worked (perhaps I forgot the port when trying the https, or the https when trying the port...).

Chris
 
Checking the Network config tab on the GUI, eth0 is not set to "autostart" so that's why it won't show up on the interfaces cat.
 
Checking the Network config tab on the GUI, eth0 is not set to "autostart" so that's why it won't show up on the interfaces cat.

neither is mine, but afaik it should be in that interfaces file, at least if your setup supports that.
that file should have been created by pve itself at install or after network modifications and reboot...

Marco
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!