I had that a few times and did several fresh resintalls. Seems it may just be you going to the login too early when behind the scenes the database is being updated.

My theory is that while the installer is 1.48, it may actually be the database one version before and then the database is updated, just as if you had an earlier version installed and then run the 1.48 update installer instead of the 1.48 full installer

Thomas seems not using proxy in his pictures. I am using proxy and using the Toems DHCP Proxy tool. It works for BIOS VM and VM loads ipxe and the screen shows its then looking for tftp IP 192.168.0.20 which is Toems server. When uefi VM boots, it loads ipxe and then it's looking for Toems on wrong IP of 192.168.0.1. No idea why it's doing this

So VM PXE boot works for legacy bios VM. Seems UEFI VM won't work for Vsphere or Proxmox

Am testing this in VM as looking to install in the company. Server 2019 TOEMS. I have toems proxy dhcp on another VM with the interface IP set and the next server as 192.168.0.20

debug shows the PXE client comms, but I noticed in the client PXE boot it shows 192.168.0.1 instead of .20?

Also, would like the Toec client to work on mobile trailers over 4G and thinking using fqdn name. Does the connection stay for data from Toems server back to client? Or would this not work due to the remote internal IP or need a dyndns solution for client?

I could just set up Toems to use internal IP and not fqdn as we have VPN tunnel to the trailers anyway?