R82.10 on Proxmox

[Moudar]

Hi all,
I am testing the installation of a Check Point SMS on Proxmox. However, every time the First Time Wizard reaches 90%, it fails, as shown in the attached screenshot.

fail.PNG

Any idea what that would be for error? maybe it is Linux error ?
disk is 200GB
8 CPU 
12GB memory

[Lesley]

did you picked the correct image? https://support.checkpoint.com/results/sk/sk158292

[Moudar]

I am using this one:

1q.PNG

[Lesley]

ISO looks good, can you check this sk?

https://support.checkpoint.com/results/sk/sk115613

[Moudar]

R82.10 is not on that link but i wiil try it and get back

[Moudar]

 ls -la /etc/.wizard_accepted
-rw-r--r-- 1 admin config 0 May 16 15:34 /etc/.wizard_accepted
[Expert@A-SMS:0]# tail -n 10 /var/log/ftw_install.log
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  password authentication failed for user "postgres"
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  password authentication failed for user "postgres"
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  password authentication failed for user "postgres"
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  password authentication failed for user "postgres"
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  password authentication failed for user "postgres"
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  password authentication failed for user "postgres"
Cannot install Check Point Security Management Server. Please contact Check Point Technical Support.
Disabling LLDP on all interfaces. originally activated to detected MHOs existence
Not SP, Disabling temporary configuration for SP detection
05/16/26 15:34:06 FTW: Complete

[Lesley]

To make sure, if you start all over with fresh machine, same issue right? The error atleast gives some info but this is a user that is created by Check Point and not you, so not that much you can do wrong. Are you able to install a gateway only system?

I think you have to ask TAC to help

[Moudar]

I haven't tested that specific gateway yet, but I did test R82 and it works fine. This leads me to suspect a Linux 5.x kernel issue—or perhaps just a need for new Proxmox tweaks that weren't required back on the older Linux 3.x kernels.

[Lesley]

Big difference between r82 and r82.10 for this scenario. 

[emmap]

What other hardware and options do you have configured? This is my config, it clean installed with no issues.

Screenshot 2026-05-18 091251.pngScreenshot 2026-05-18 091416.png

[Moudar · Accepted solution]

Late last night, I switched the network device from virtio to e1000, and it's working fine now. As I suspected, there seems to be a Linux-specific issue causing the installation to fail. I'm not sure if my lab environment requires e1000 specifically, though.

1q.PNG

I encountered similar issues with a Check Point R82.10 cluster in another lab; the sync traffic would work for a few minutes and then crash. I’ll start a separate thread about that once I have that environment up and running again.

[emmap]

I'm surprising it's working with e1000, it's not meant to be supported in R82.10 and higher. 

https://support.checkpoint.com/results/sk/sk180572 

Virtio is officially supported though, so if that is the issue then it might be worth a TAC case to investigate.

[Moudar]

That is not a production environment, it is only to test R82.10

but very strange, i think it is about Proxmox and EVE and how we configure them
I will reinstall with virtio and test

[the_rock]

Glad it works for you!

[PhoneBoy]

Weird, because I am using virtio as my NIC drivers without issue. 
That said, the ISO I set my system up with is Take 464 (not Take 467).

[PeterH]

On my Site Proxmox start sucessfull after installation done as well the first time wizard successful finished.

But after rebooting to succeed first time Wizard the configured gateway reboot in a circle and never stops.

Any Idea?

[PhoneBoy]

Most likely, it's the issue I identified a few months back: https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-Promox/m-p/266159#M5657

[PeterH]

Cool, thank you. It was not enought to change only the CPU Type to Intel. Afterwards I have to reinstall the OS once more from the ISO image. Now it works as expected.

It looks like the first time wizard manipuletas some thing different when coosing Gateway only or Management only. Management only worked also well with default CPU Type, while Gateway needs Intel Type.

[PhoneBoy]

The only thing FTW is doing in this regard is setting the device type (gateway, management, or bothI.
Gateways require loading kernel modules, which undoubtedly have processor-specific code in them.