Resolving Proxmox VM Connectivity Issue

The issue is that virtual machines with public IP addresses from the subnet can generally access the internet and load standard websites, but certain functions such as ping, traceroute, speed tests, and Let’s Encrypt certificate validation consistently fail. Notably, only the first assigned address works reliably, while subsequent addresses from the routed subnet cannot establish full connectivity. In contrast, the internal networks using NAT operate without any problems, including internet access and speed tests. This strongly suggests a misconfiguration in packet forwarding or an incomplete routing setup between the host, the router VM, and the public network.

The current environment is built on a dedicated server running Proxmox, with a router VM in front that is intended to handle both public and internal. However, the routed public subnet continues to cause problems as described above. We are looking for a freelancer to thoroughly analyze the entire data path from the provider through the host and router VM to the individual virtual machines, identify the root cause, and implement a corrected configuration. The end goal is a cleanly working setup where all public IPs are usable, connectivity is stable for all protocols and services, and the firewall remains restrictive but functional. Further maintaining the clear documentation of all changes and configurations is expected.