[ANNOYED] can't access fresh install proxmox server

N

nokia3310

Guest
Ok..things like this just annoy me every time.
Why is it that things can't go right?

I followed all installation instructions and now it is time to access the web GUI of the fresh install of proxmox and i can't. The proxmox server will not ping or anything..basically the network is not working. To make matters worse every time i try /etc/init.d/networking start or restart or anything it tells about some deprecated thing and that i should try grep --help
Now i even tried sudo service networking start or restart and same problem.

So my question here is one in hell do i get network to start?
What really annoys me is why is it that things cant be done so that things like this are avoided?
just frustrated at the moment

I have wifi on and also have wired connection through ethernet cable as well


Code:
/etc/network/interfaces
Code:
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 192.168.100.2
        netmask 255.255.255.0
        gateway 192.168.100.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

So how do i get my network to start working?

Also i am trying to access the proxmox server from https://192.168.100.2:8006 from a windows machine with the following

Code:
ip 192.168.1.13
netmask 255.255.255.0
gateway 192.168.1.1
 
Last edited by a moderator:
looks like your NIC is not supported.? provide details about your hardware.
 
looks like your NIC is not supported.? provide details about your hardware.

Dell Latitude Laptop E4300 4GB RAM, 150GB Storage, core 2 duo

I had KVM installed on it which worked perfectly fine..i just installed proxmox on top of the KVM for a fresh/clean install...so not sure why it is not supported
 
Are good on networking, so for sure the two gateways, working on different subnets, let the traffic pass, or are you just doing a big mistake?
Also in /etc/network/interfaces I don't see:
iface eth0 inet manual
before bridge definition (and after the loopback one)
 
should have a intel gigabit nic, please confirm. our installation ISO includes driver for almost all intel nics.

check dmesg and post the output of 'lspci -v'

just to note, wireless is not supported.
 
Are good on networking, so for sure the two gateways, working on different subnets, let the traffic pass, or are you just doing a big mistake?
Also in /etc/network/interfaces I don't see:
iface eth0 inet manual
before bridge definition (and after the loopback one)

I did add that and still nothing happened

and my question is why is that omitted...arent all default config suppose to be the same?
 
should have a intel gigabit nic, please confirm. our installation ISO includes driver for almost all intel nics.

check dmesg and post the output of 'lspci -v'

just to note, wireless is not supported.

How do i check for the intel gigabit nic?

How do i post the output of "dmesg" and "lspci -v" ? when the proxmox server has no browser to copy and paste the output? And i cannot try writing down the output..really long
 
Last edited by a moderator:
How do i check for the intel gigabit nic?

How do i post the output of "dmesg" and "lspci -v" ? when the proxmox server has no browser to copy and paste the output? And i cannot try writing down the output..really long

you do not need post the full output, just check the dmesg output for messages about your nic and network.

> dmesg | less

> lspci -v | less

shows the hardware. find the NIC and check the found hardware and the used driver
 
I mean, you are trying to talk from your pc that is in the subnet
192.168.1.0
to proxmox that is on another subnet:
192.168.100.0
if you don't have 2 routers properly configured (or additional routing rules on your hosts), they can't talk.
Try to set your pc with the address 192.168.100.13 instead of 192.168.1.13 and let me know
BTW, you are right that the eth0 line is not automatically set in very last proxmox installation, but seems that is not fundamental so things work anyway
 
you do not need post the full output, just check the dmesg output for messages about your nic and network.

> dmesg | less

> lspci -v | less

shows the hardware. find the NIC and check the found hardware and the used driver

It shows intel and there are so many kernel drivers i see not sure which one you need. the NIC is intel

Also remember i just said i ran KVM on it and it had no problem...so how will proxmox have a problem?
 
I mean, you are trying to talk from your pc that is in the subnet
192.168.1.0
to proxmox that is on another subnet:
192.168.100.0
if you don't have 2 routers properly configured (or additional routing rules on your hosts), they can't talk.
Try to set your pc with the address 192.168.100.13 instead of 192.168.1.13 and let me know
BTW, you are right that the eth0 line is not automatically set in very last proxmox installation, but seems that is not fundamental so things work anyway

I think the first thing is i need to get network working first..i cannot even access anything...no ping...no update nothing...if i can get the network to work then i think i can find my way around
 
In fact, is what I'm suggesting you, but you don't test neither provide explaination about why, if your PC is woring on one subnet, you expect proxmox to work on another one and the two ping each other.
How can you expect a ping from your pc to proxmox to work, if they are on different subnets? Do you really have a router with IP 192.168.100.1? Are you able to ping, from proxmox, 192.168.100.2? If so, what about 192.168.100.1? If you change your PC address to 192.168.100.13, can you ping 192.168.100.1 instead? etc.
I've the feeling you are missing the basic of IP networking, is not a proxmox problem, is a badly configured networking parameters instead, OMHO.
 
In fact, is what I'm suggesting you, but you don't test neither provide explaination about why, if your PC is woring on one subnet, you expect proxmox to work on another one and the two ping each other.
How can you expect a ping from your pc to proxmox to work, if they are on different subnets? Do you really have a router with IP 192.168.100.1? Are you able to ping, from proxmox, 192.168.100.2? If so, what about 192.168.100.1? If you change your PC address to 192.168.100.13, can you ping 192.168.100.1 instead? etc.
I've the feeling you are missing the basic of IP networking, is not a proxmox problem, is a badly configured networking parameters instead, OMHO.

Did you read my last post? I said all i need is network to start working...i can fix subnet issue....that is not a problem..right now network in is not working on the proxmox debian server
 
You are like one saying "I can't enter my home", and at the reply "you have to open the door first" replies "but I have to enter my home first!"
How can you tell "is not working"?
- Just because some warning about something deprecated? It could be a minor problem and networking be working fine
- because you can't ping it from a PC that is outside it's subnet? It will NEVER work, so is an useless test
so go on proxmox, plug a video and a keyboard, and do the above tests and report back.
 
You are like one saying "I can't enter my home", and at the reply "you have to open the door first" replies "but I have to enter my home first!"
How can you tell "is not working"?
- Just because some warning about something deprecated? It could be a minor problem and networking be working fine
- because you can't ping it from a PC that is outside it's subnet? It will NEVER work, so is an useless test
so go on proxmox, plug a video and a keyboard, and do the above tests and report back.

Ok i cannot ping the proxmox server from within the proxmox CLI itself. Lets forget the windows PC exist...the networking to access inthernet on the proxmox server does not work. Forget about who can view it from outside..the server cannot do "aptitude update"
 
You are like one saying "I can't enter my home", and at the reply "you have to open the door first" replies "but I have to enter my home first!"
How can you tell "is not working"?
- Just because some warning about something deprecated? It could be a minor problem and networking be working fine
- because you can't ping it from a PC that is outside it's subnet? It will NEVER work, so is an useless test
so go on proxmox, plug a video and a keyboard, and do the above tests and report back.

Ok i am reinstalling proxmox all over so i can set the IP subnet to match the subnet of my windows PC just to move on from what you said. Hope things go well
 
WORKED! now

This is what happened.
When i first installed proxmox...i did not connect the ethernet cable and was hoping on using wifi (stupid me i guess)
So then the IP selected was in a different subnet to the network of my windows PC.

Anyways when i reinstall again with the ethernet cable installed right from beginning...the IP selected was in the same subnet as my windows PC and everything worked like a charm!

Thanks to @mmenaz and @tom
 
Just to be sure, what do you mean with "on top of teh KVM"? Inside of a KVM guest or Proxmox completely replaced the OS on Dell Latitude? (= Dell Latitude boots with proxmox?)
 
Just to be sure, what do you mean with "on top of teh KVM"? Inside of a KVM guest or Proxmox completely replaced the OS on Dell Latitude? (= Dell Latitude boots with proxmox?)

Completely replaced the whole entire OS (bare metal)...installed the proxmox from CD iso image.
 
One last question i have...my computer has 150GB but proxmox only has ~ 90GB...where did 60GB go to?
 

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!