[SOLVED] Can't acces proxmox after Firewall enabled ,OVH server goes rescue mode

Sikjairi · Aug 26, 2020

Hi Guys ,
Could someone help please , when i activated the firewall from GUI interface i lose all acces to the proxmox server "OVH" and the server goes to the rescue mode ,how can i resolve the probleme please because we can't acces to the running VMs , and i can't found pve-firewall in rescue mode to try disable firewall . Thank you in advance.

Code:

root@rescue:~# fdisk -l

Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0bb00994

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         4096  40962047  40957952  19.5G fd Linux raid autodetect
/dev/sda2        40962048 102399999  61437952  29.3G fd Linux raid autodetect
/dev/sda3       102400000 937695231 835295232 398.3G  f W95 Ext'd (LBA)
/dev/sda5       102402048 937695231 835293184 398.3G fd Linux raid autodetect

Disk /dev/sdb: 447.1 GiB, 480103981056 bytes, 937703088 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xdebf1d52

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sdb1  *         4096  40962047  40957952  19.5G fd Linux raid autodetect
/dev/sdb2        40962048 102399999  61437952  29.3G 82 Linux swap / Solaris
/dev/sdb3       102400000 937695231 835295232 398.3G  f W95 Ext'd (LBA)
/dev/sdb5       102402048 937695231 835293184 398.3G fd Linux raid autodetect

Disk /dev/md5: 398.3 GiB, 427670044672 bytes, 835293056 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/md1: 19.5 GiB, 20970405888 bytes, 40957824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/pve-data: 394.3 GiB, 423373045760 bytes, 826900480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

root@rescue:~# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 16G 0 16G 0% /dev
37.59.1.237:/home/pub/rescue.v8 1.9T 333G 1.5T 18% /nfs
tmpfs 16G 25M 16G 1% /rw
aufs 16G 25M 16G 1% /
37.59.1.237:/home/pub/pro-power 1.9T 333G 1.5T 18% /power
37.59.1.237:/home/pub/commonnfs 1.9T 333G 1.5T 18% /common
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 98M 16G 1% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
tmpfs 16G 12K 16G 1% /tmp
/dev/mapper/pve-data 388G 296G 73G 81% /mnt

tom · Aug 26, 2020

Sikjairi said:
Hi Guys ,
Could someone help please , when i activated the firewall from GUI interface i lose all acces to the proxmox server "OVH" and the server goes to the rescue mode ,how can i resolve the probleme please because we can't acces to the running VMs , and i can't found pve-firewall in rescue mode to try disable firewall . Thank you in advance.
...

Seems you enabled active OVH monitoring (enabled by default). So if you block this access by activating the firewall, OVH reboots your host automatically into rescue mode, so this is expected.

=> disable this active monitoring via your OVH panel.

Sikjairi · Aug 27, 2020

tom said:
Seems you enabled active OVH monitoring (enabled by default). So if you block this access by activating the firewall, OVH reboots your host automatically into rescue mode, so this is expected.

=> disable this active monitoring via your OVH panel.

Greaatttt Thank you Tom !!! it works like a charm

Just another question Please, What is the easiest way to forward web traffic from outside " Public IP" to my local web server "Private IP" on proxmox "OVH"

Thank you .

oguz · Aug 27, 2020

Sikjairi said:
Just another question Please, What is the easiest way to forward web traffic from outside " Public IP" to my local web server "Private IP" on proxmox "OVH"

you can set up a private subnet for your CTs/VMs and use port forwarding on the host to do that. see[0]

[0]: https://pve.proxmox.com/wiki/Networ...ith_tt_span_class_monospaced_iptables_span_tt

Sikjairi · Aug 28, 2020

oguz said:
you can set up a private subnet for your CTs/VMs and use port forwarding on the host to do that. see[0]

[0]: https://pve.proxmox.com/wiki/Networ...ith_tt_span_class_monospaced_iptables_span_tt

Thank you a lot of @oguz i will do that , thank you all for your support.

Sikjairi · Sep 1, 2020

oguz said:
you can set up a private subnet for your CTs/VMs and use port forwarding on the host to do that. see[0]

[0]: https://pve.proxmox.com/wiki/Networ...ith_tt_span_class_monospaced_iptables_span_tt

it works for me & for the port forwarding i used NGINX ,Thank you all for your support ,

oguz · Sep 1, 2020

great, you can mark the thread [SOLVED] so others know what to expect

S4hosting · Sep 10, 2022

tom said:
Seems you enabled active OVH monitoring (enabled by default). So if you block this access by activating the firewall, OVH reboots your host automatically into rescue mode, so this is expected.

=> disable this active monitoring via your OVH panel.

i have configured firewall wrongly now cant access my server i have followed ur procedure,but still cant fix my server ip blocking by firewall

Search

Search

[SOLVED] Can't acces proxmox after Firewall enabled ,OVH server goes rescue mode

Sikjairi

Active Member

tom

Proxmox Staff Member

Sikjairi

Active Member

oguz

Proxmox Retired Staff

Sikjairi

Active Member

Sikjairi

Active Member

oguz

Proxmox Retired Staff

S4hosting

Member