[SOLVED] Cannot access SSH & Web GUI

[sayoakin]

I am new to Proxmox (love it so far) and don't know exactly where to put this here but here is my problem.

My proxmox node was working fine at OVH until I tried to create a new Linux Bridge.
Not sure what I did wrong but I created and applied configuration. It wasn't looking like it
was working so I did a restart.

Since then I can't access the GUI, SSH is refusing connection.
The only thing that works right now is SSH when I enter rescue mode.

I need help please.

Thank you

 

[oguz]

hi,

Not sure what I did wrong but I created and applied configuration. It wasn't looking like it
was working so I did a restart.

Since then I can't access the GUI, SSH is refusing connection.

probably you've reconfigured your network in a wrong way, so your node doesn't have network access (just my guess).

The only thing that works right now is SSH when I enter rescue mode.

I need help please.

can you view the /etc/network/interfaces file from there? you might have to mount your root filesystem in the rescue environment first.

i'm assuming you had/wanted a default network configuration with a simple bridge [0]

if you need any help editing the network configuration file please post the contents of it here.

hope this helps!

[0]: https://pve.proxmox.com/wiki/Network_Configuration#_default_configuration_using_a_bridge

 

[sayoakin]

/etc/network/interfaces

# interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d

 

[oguz]

/etc/network/interfaces

# interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d

is this from your rescue environment or your mounted PVE root filesystem?

you need to edit the one that PVE uses that means mounting the disk that PVE is residing on.
if you have trouble please post the output of lsblk -f.

otherwise see the above link for example network configuration.

 

[sayoakin]

is this from your rescue environment or your mounted PVE root filesystem?

you need to edit the one that PVE uses that means mounting the disk that PVE is residing on.
if you have trouble please post the output of lsblk -f.

otherwise see the above link for example network configuration.

This is from rescue

 

[sayoakin]

if you have trouble please post the output of lsblk -f.

root@rescue:~# lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sdd
├─sdd2 linux_ra md2 59cff9b0-f6ae-ab93-c1e5-f955f607fb19
│ └─md126 ext4 root 3afe47ee-4174-43be-ad44-cfc75d1697c8
├─sdd3 swap swap-sdd3
d5022659-9e71-4faa-a842-e7973dabe74c
├─sdd1 vfat EFI_SYSPART
2AD3-5FFF
└─sdd4 linux_ra md4 4b5ed492-1349-c87b-a0f6-34d4323134ce
└─md127 LVM2_mem AhhUOf-sbqC-XNlW-jPa5-n6cl-B6Ac-M0amQ9
└─vg-data ext4 var-lib-vz
869e8c7e-a0af-41b9-9c48-db3560ad979a
sdb
├─sdb4 linux_ra md4 4b5ed492-1349-c87b-a0f6-34d4323134ce
│ └─md127 LVM2_mem AhhUOf-sbqC-XNlW-jPa5-n6cl-B6Ac-M0amQ9
│ └─vg-data ext4 var-lib-vz
869e8c7e-a0af-41b9-9c48-db3560ad979a
├─sdb2 linux_ra md2 59cff9b0-f6ae-ab93-c1e5-f955f607fb19
│ └─md126 ext4 root 3afe47ee-4174-43be-ad44-cfc75d1697c8
├─sdb3 swap swap-sdb3
f6cab3e7-3441-40a3-95a0-d25d58f57028
└─sdb1 vfat EFI_SYSPART
2A78-0C0D
sdc
├─sdc2 linux_ra md2 59cff9b0-f6ae-ab93-c1e5-f955f607fb19
│ └─md126 ext4 root 3afe47ee-4174-43be-ad44-cfc75d1697c8
├─sdc3 swap swap-sdc3
b4c631b9-7d22-4f56-8132-ae5902dc6dbb
├─sdc1 vfat EFI_SYSPART
2AA5-F3B0
└─sdc4 linux_ra md4 4b5ed492-1349-c87b-a0f6-34d4323134ce
└─md127 LVM2_mem AhhUOf-sbqC-XNlW-jPa5-n6cl-B6Ac-M0amQ9
└─vg-data ext4 var-lib-vz
869e8c7e-a0af-41b9-9c48-db3560ad979a
sda
├─sda4 linux_ra md4 4b5ed492-1349-c87b-a0f6-34d4323134ce
│ └─md127 LVM2_mem AhhUOf-sbqC-XNlW-jPa5-n6cl-B6Ac-M0amQ9
│ └─vg-data ext4 var-lib-vz
869e8c7e-a0af-41b9-9c48-db3560ad979a
├─sda2 linux_ra md2 59cff9b0-f6ae-ab93-c1e5-f955f607fb19
│ └─md126 ext4 root 3afe47ee-4174-43be-ad44-cfc75d1697c8
├─sda5 iso9660 config-2 2021-12-24-11-36-53-00
├─sda3 swap swap-sda3
af0b3d59-f5cd-4b73-8312-3ce4e04bafa9
└─sda1 vfat EFI_SYSPART
2A4A-871C

 

[oguz]

okay, to mount your root filesystem try the following:

vgs -a # should show you "pve" by default
vgchange -ay # activate the volume groups
lvs # shows you logical volumes, look for "root"
mkdir /mnt/pve-root # create a directory
mount /dev/mapper/pve-root /mnt/pve-root # change "pve-root" to the actual name of your logical volume if it's different

afterwards you should be able to cd into /mnt/pve-root directory and make your changes there to the interfaces file in /mnt/pve-root/etc/network/interfaces.

 

[sayoakin]

Should I do all these from the resuce mode because that is the only thing that works right now?
Please I hope this won't cause loss of data because I have everything on this device.
Thank you for your help

 

[oguz]

Should I do all these from the resuce mode because that is the only thing that works right now?

yes... in case it's not clear:

1. in rescue mode, you're in a different filesystem than in your regular PVE installation
2. so you have to mount your PVE's root filesystem onto your rescue mode (follow instructions in the above post for that)
3. afterwards you can edit the network configuration of your PVE host on the mounted filesystem

when that's all done you can reboot into your regular PVE.
if the network is configured correctly, you should be able to access it as normal.

 

[oguz]

Please I hope this won't cause loss of data because I have everything on this device.

that shouldn't happen, as long as you don't delete anything or wipe your disk somehow

 

[sayoakin]

that shouldn't happen, as long as you don't delete anything or wipe your disk somehow

Ok. Thank you
Doing this now.

Should I reboot normally outside rescue when this is done?

 

[oguz]

Should I reboot normally outside rescue when this is done?

yeah, if you still cannot reach your PVE after the reboot without rescue, then most likely there's an error inside the configuration file.

 

[sayoakin]

Sorry if I am not getting it fast, I am a bit new to all these.
root@rescue:/# vgs -a VG #PV #LV #SN Attr VSize VFree vg 1 1 0 wz--n- 1.80t 0 root@rescue:/# vgchange -ay 1 logical volume(s) in volume group "vg" now active root@rescue:/# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert data vg -wi-a----- 1.80t root@rescue:/# mkdir /mnt/pve-root root@rescue:/# mount /dev/mapper/pve-root /mnt/pve-root mount: special device /dev/mapper/pve-root does not exist root@rescue:/# cd /mnt/pve-root root@rescue:/mnt/pve-root#

Thank you for your help and patience

 

[oguz]

Sorry if I am not getting it fast, I am a bit new to all these.

my bad, it looks like your root filesystem is not using the LVM after all

you should be able to just mount the ext4 root partition from md-raid:

mount /dev/md126 /mnt/pve-root
cat /mnt/pve-root/etc/network/interfaces # should show you the PVE network config

if that worked, you can edit the configuration file with a terminal text editor like nano or vi//vim depending on what the rescue environment has available.

 

[sayoakin]

Thank you.
On it. I see the network interfaces and I removed vmbr1 which was what I added last.
Rebooting now and hope it works.

 

[sayoakin]

my bad, it looks like your root filesystem is not using the LVM after all

you should be able to just mount the ext4 root partition from md-raid:

mount /dev/md126 /mnt/pve-root
cat /mnt/pve-root/etc/network/interfaces # should show you the PVE network config

if that worked, you can edit the configuration file with a terminal text editor like nano or vi//vim depending on what the rescue environment has available.

You are a genius!
This worked perfectly and I am back in business.
Still loving Proxmox!

Thank you so very much

 

[oguz]

You are a genius!
This worked perfectly and I am back in business.
Still loving Proxmox!

Thank you so very much

glad to be of help!

you can mark the thread as [SOLVED]