lost ip address of proxmox ve

W

wbravin

Member
Sep 7, 2022
71
6
13
Hello all

I screwed up.

My proxmox server all it's vm and LXC are up

however i cannot access my pve dashboard because i no longer know the ip address of my proxmox server nor does it show up in my router in the list of attached devices

How do i find out how to access this dashboard

Thank you for the assistance
 
wbravin said:
My proxmox server all it's vm and LXC are up

however i cannot access my pve dashboard because i no longer know the ip address of my proxmox server nor does it show up in my router in the list of attached devices
Click to expand...
Login to the Proxmox host console (using a physical keyboard and display) and look at the output of ip a | grep inet command?
 
  • Like
Reactions: waltar
leesteken said:
Login to the Proxmox host console (using a physical keyboard and display) and look at the output of ip a | grep inet command?
Click to expand...
Thank you for prompt reply

hooked up kb and monitor presented ip of 192.168.1.125
did ip a ! grep net
inet 127.0.0.1/8 scope host
inet6 fe: :baca:3aff:f5:8467/64 scope link
net6 fe: :baca:3aff:f5:8466/64 scope link
net6 fe: :baca:3aff:f5:8465/64 scope link
net6 fe: :baca:3aff:f5:8464/64 scope link

link/ether fe:de:89:0d:9c:bf brd ff:ff:ff:ff:ff:ff link-netnsid 0
link/ether fe:a1:d8:36:86:01 brd ff:ff:ff:ff:ff:ff link-netnsid 1


when i type 192.168.1.125:8006 in chrome search bar i get a time out
 
wbravin said:
did ip a ! grep net
inet 127.0.0.1/8 scope host
inet6 fe: :baca:3aff:f5:8467/64 scope link
net6 fe: :baca:3aff:f5:8466/64 scope link
net6 fe: :baca:3aff:f5:8465/64 scope link
net6 fe: :baca:3aff:f5:8464/64 scope link
Click to expand...
! should be a | but the output looks plausible; there appears to be no IP set for Proxmox. The 192.168.1.125 probably comes from /etc/hosts.
Please show (the actual) output (maybe by posting a photo) of cat /etc/network/interfaces.
 
Hello

Thank you for your reply
Sorry for the mistake I did correct ip a line mistake it produced
127.0.0.1 local hosts, local domain local.host
192.168.1.125 pve home

:: 1 ip6 local host -ip6 loopback
feoo: :0 Local net
ff00: ;0 ip6 local net
ff00: ;1 ip6 all nodes
ff00::2 ip6 all routers
ff00::3 ip6 all hosts

I took 2 pictures of the results of host and interfaces however this site tells me the files are foo big hao can i share them with you?
 
Last edited:
You basically do not have any IP assigned.

Check what you have done to your /etc/network/interfaces.

Do you have an idea what IP you want to have? Or just consider DHCP and forget this issue altogether.
 
thank you very much for your prompt reply

I am of the same opinion i have no IP4 address

I would like to have 192.168.1.120 this would be my choice ip to access proxmox

although opnsens wa deleted, I would like to keep 1 port for lan 192.168.1.3 and one port for wan this will be 192.168.1.122 Opnsens will not be live until Jan25. This i will assign when i configure opnsens on proxmox

I tend to stay away from dhcp (just think non dhcp connects betters ) not sure why

how can an i assign the proxmox ip address manually from a command line
 
Last edited:
You can just edit: nano /etc/network/interfaces

And then depending on what you want, add the static IP to your desired interface.

The stock install e.g. leaves you with (example):

Code: 
iface vmbr0 inet static
    address 10.10.10.10/24
    gateway 10.10.10.1

The static address must match the one provided in /etc/hosts
 
  • Like
Reactions: waltar
thank you for your patience and reply
nano /etc/hhost shows
127.0.0.1 as localhost
192.168.1.125 as pve.home

i did edit interfaces
auto vmbr0
iface vmbr0 inet static
address 192.168.1.125/24
gateway 192.168.1.1
bridge-ports en01
bridge-stp off
bridge-vlan-aware yes
bridge-vids 2-4094

all lines properly tabed as other interfaces

source /etc/network/interfaces.d/"

still cannot access https://192.168.1.125:8006 (or http)

i get time out

i trully do not know how i screwed this up verry frustrating

again thank you for your patience
 
wbravin said:
thank you for your patience and reply
nano /etc/hhost shows
127.0.0.1 as localhost
192.168.1.125 as pve.home

i did edit interfaces
auto vmbr0
iface vmbr0 inet static
address 192.168.1.125/24
gateway 192.168.1.1
bridge-ports en01
bridge-stp off
bridge-vlan-aware yes
bridge-vids 2-4094

all lines properly tabed as other interfaces

source /etc/network/interfaces.d/"

still cannot access https://192.168.1.125:8006 (or http)

i get time out

i trully do not know how i screwed this up verry frustrating

again thank you for your patience
Click to expand...

Have you rebooted? :) Sorry I should have emphasized either a reboot or systemctl restart networking
 
esi_y said:
Have you rebooted? :) Sorry I should have emphasized either a reboot or systemctl restart networking
Click to expand...
Thank you.

I did rebout the whole system several times and i did a systemctl daemon reload thinking this would do it.... it did not

idid a systemctl restart network and the got me to the dashboard


thank you
 
  • Like
Reactions: esi_y
hello

following the interaction here above, i tried to install opnsense as a vm which went horribly wrong because it got installed as a gateway (192.168.1.1) which conflicted with my current router to the point i could not reach the router. yuk

I finally fixed the network issue and i tried to access tuenas and HA as i do first thing every morning. No joy
I try to log into proxmox . no way

I connected the server to monito and KB. Proxmox dos load and presents at the top screen with ip 192.168.1.125

i try to edit the /etc/network/interfaces and tried to change the ip of the vcmbr0 static to 192.168.1.125.

i cannot access the dashboard ard the vms and the lxcs are not stared

however thinterfaces file come up as unwritable as do many of the conf file i have. this meas i cannop see my mails and documents.

should i bitr the bullet and re install proxmox?

If so i will need to document all the conf files on paper correct?

or is there )hopefully) a simpler and faster process?


Thank you for your patience
 
Last edited:
wbravin said:
following the interaction here above, i tried to install opnsense as a vm which went horribly wrong because it got installed as a gateway (192.168.1.1) which conflicted with my current router to the point i could not reach the router. yuk
Click to expand...

I would not be running these setups myself, but I know they are popular. I do not think it really matters if this happens, you can always take the VM down from local console. But if you know this is what you are about to be doing, maybe give such VM a bogus network interface that is NOT bridged with your host to begin with.

wbravin said:
I finally fixed the network issue and i tried to access tuenas and HA as i do first thing every morning. No joy
I try to log into proxmox . no way
Click to expand...

This sounds entirely like network issue.

wbravin said:
I connected the server to monito and KB. Proxmox dos load and presents at the top screen with ip 192.168.1.125
Click to expand...

PVE is not really smart about this, it is showing you whatever was configured, if I have to guess, in /etc/hosts. If you run DHCP, it will not show you anything. You can completely disregard this MOTD text.

wbravin said:
i try to edit the /etc/network/interfaces and tried to change the ip of the vcmbr0 static to 192.168.1.125.

however thinterfaces file come up as unwritable as do many of the conf file i have

should i bitr the bullet and re install proxmox?
Click to expand...

Are you doing this in the console? I am not sure how /etc/network/interfaces would not be writeable.

wbravin said:
If so i will need to document all the conf files on paper correct?

or is there )hopefully) a simpler and faster process?
Click to expand...

You can always copy the files on e.g. USB flash drives.

wbravin said:
Thank you for your patience
Click to expand...

No worries. I think you just have network conflict, but you said very little about your network topology now, or at least intended one.
 
hello

following the interaction here above, i tried to install opnsense as a vm which went horribly wrong because it got installed as a gateway (192.168.1.1) which conflicted with my current router to the point i could not reach the router. yuk

I finally fixed the network issue and i tried to access tuenas and HA as i do first thing every morning. No joy
I try to log into proxmox . no way

I connected the server to monito and KB. Proxmox dos load and presents at the top screen with ip 192.168.1.125

i try to edit the /etc/network/interfaces


root
r
esi_y said:
I would not be running these setups myself, but I know they are popular. I do not think it really matters if this happens, you can always take the VM down from local console. But if you know this is what you are about to be doing, maybe give such VM a bogus network interface that is NOT bridged with your host to begin with.



This sounds entirely like network issue.



PVE is not really smart about this, it is showing you whatever was configured, if I have to guess, in /etc/hosts. If you run DHCP, it will not show you anything. You can completely disregard this MOTD text.



Are you doing this in the console? I am not sure how /etc/network/interfaces would not be writeable.



You can always copy the files on e.g. USB flash drives.



No worries. I think you just have network conflict, but you said very little about your network topology now, or at least intended one.
Click to expand...
thank you for your comments

i mnanaged to re
 
wbravin said:
hello

following the interaction here above, i tried to install opnsense as a vm which went horribly wrong because it got installed as a gateway (192.168.1.1) which conflicted with my current router to the point i could not reach the router. yuk

I finally fixed the network issue and i tried to access tuenas and HA as i do first thing every morning. No joy
I try to log into proxmox . no way

I connected the server to monito and KB. Proxmox dos load and presents at the top screen with ip 192.168.1.125

i try to edit the /etc/network/interfaces


root
r
Click to expand...
Thank you for your time and for the comments.

I did finally re-established my network and now i have access to the web.

All the vms and lxcs were working prior to my idea of installing Jellyfin as an lxc. (which i managed to achieve). I then when it was up and runni9ng I deleted it .

all vms and lxc were running well at this time


It is wen i was installing opnsense and i played with the bridged network is when i started to cause this massive debacle.

I did do try to edit this in the console and logged in as root and still the *.conf filed were unwritable

You suggest to copy the file to a usb stick

i presume you are taking about the vm's and lxc's files . Although this may be simple to do I am sure that i would find a way to screw this up



My network is simple


satellite dish to dish amplifier to asus router to powerline to netgear managed switch to servers and other simple switches to pcs, printers or to an other powerline to an other switch to local devices (HTPC amplifier tv)


the servers are main server (dell r720 with proxmox) (Dell r710 stand by (just started to build it to act ad test bed to avoid these situations) a sumpermicro that is my backup server (i can access) and finally a home built server (this was my first venture)

Since i can reach the server via console and see the ip 192.168.1.125 and i cant reach this server from an other pc.
I would suggest that the network of this server is recognized and that these interfaces at /etc/network/interfaces are present, I feel that there could be a conflict the console, host shows no ip4 address and the interfaces showing 192.168.1.120.

oops forgot to mention my router does show the proxmox mgmt at 192.168.1.120


This i where i loose my confidence I'm certain there a way to fix this


What should i do?

Thank you for your support
 
Last edited:
wbravin said:
It is wen i was installing opnsense and i played with the bridged network is when i started to cause this massive debacle.

I did do try to edit this in the console and logged in as root and still the *.conf filed were unwritable
Click to expand...

I am not sure which config files you mean, but I assume those in /etc/pve/... path.

That is not a problem on its own, you probably have mismatch in what is in:
- /etc/network/interfaces
and
- /etc/hosts

You can also explicitly check what problem you have with:

journalctl -b -e

(you can scroll around and press Q when done, if there's something noteworthy you can even take picture of the screen)

I just find it very unlikely that your /etc/network/interfaces is not writeable.

wbravin said:
You suggest to copy the file to a usb stick

i presume you are taking about the vm's and lxc's files . Although this may be simple to do I am sure that i would find a way to screw this up
Click to expand...

You asked if you should be writing things down by pencil and paper. :) That's not necessary, if you have to keep copy of configs, you can copy them out. That is, if you were going to reinstall it. But I think you should at least check if you indeed cannot write to the files mentioned above and also if that was the case, the log. It sounds something minor to me.

wbravin said:
Since i can reach the server via console and see the ip 192.168.1.125 and i cant reach this server from an other pc.
Click to expand...

I do not think you "see" any IP, whatever IP that PVE prints you above login is completely to be ignored in this situation. This is the issue with static IPs, even if you have e.g. working DHCP on that segment (whatever it would be, your actual router or some *Sense), your PVE will never get IP from it and if your PVE is on different subnet it's not routable, or even you could have IP conflict (something else was assigned the same IP by DHCP that you statically assigned to PVE).

wbravin said:
I would suggest that the network of this server is recognized and that these interfaces at /etc/network/interfaces are present, I feel that there could be a conflict the console, host shows no ip4 address and the interfaces showing 192.168.1.120.
Click to expand...

I am not sure what you refer to as "console" - these are servers, so it could be physical console or iDRAC. Forget the GUI or SSH for this kind of situation, you need to set proper IP to your server that is routable on the segment it is in. It is important to know what routers (real or virtual) you have there to even guess what's going on. I am not sure if your virtual one is off and how the the network configuration looks (you could post a picture from /etc/network/interfaces).

wbravin said:
oops forgot to mention my router does show the proxmox mgmt at 192.168.1.120
Click to expand...

When you say mgmt, I can only guess you mean iDRAC. That's fine, but it has no bearing on your other interface or Linux network config.

wbravin said:
This i where i loose my confidence I'm certain there a way to fix this


What should i do?
Click to expand...

Edit the two files mentioned above, if they are not editable, find out why (is the entire filesystem read-only?), check if you can e.g. create file (touch t) and post their content.

wbravin said:
Thank you for your support
Click to expand...

Do not overthink it, just make sure the server has proper network config. If need be, you will reboot it and configure from e.g. LIVE Debian.
 
  • Like
Reactions: wbravin
hi



after doing a journalctl -b -e i got 954 lines most of which were error of the type
local/pve-ssl.key
and
var/logpveproxxy/access.key
or private guest map
iether not loaded, not readable or read only

its realy a mess
 
wbravin said:
after doing a journalctl -b -e i got 954 lines most of which were error of the type
local/pve-ssl.key
and
var/logpveproxxy/access.key
or private guest map
iether not loaded, not readable or read only
Click to expand...

Yes because :)

https://forum.proxmox.com/threads/f...-key-failed-to-load-local-private-key.155771/

This happens so often due to bad error messages of PVE that I made the piece for it. :D

wbravin said:
its realy a mess
Click to expand...

You should be focusing on:

esi_y said:
That is not a problem on its own, you probably have mismatch in what is in:
- /etc/network/interfaces
and
- /etc/hosts
Click to expand...
 
esi_y said:
Yes because :)

https://forum.proxmox.com/threads/f...-key-failed-to-load-local-private-key.155771/

This happens so often due to bad error messages of PVE that I made the piece for it. :D

thank you for this

You should be focusing on:
Click to expand...
there is a mismatch between the 2. in addition from the little i know there is an user file, a credential files and last but not least network issues.

i've decided to bite the bullet. i will re-install from scatch proxmox. with what i have learned i will increase the size of both drives at this before the reinstall

on monday i i will start the additions of the ha then trunas then wireguard and finally pihole. i am considering installing bare meta opnsense on a mini pc

thank you very much for your contribution
 
You must log in or register to reply here.
Top Bottom