Whenever you face vps network issue, whether its a fresh vps with fresh ip pool or for an existing ip pool, check for any blocking done by your ip provider or if any firewall is enabled either on Ip provider panel or on your server.
If you feel everything is fine there, then check if vps is booted as expected. You can view it in vnc from panel.
Also make sure if vps firewall is not blocking your connections.
If vps is getting pinged or ssh then there is some service issues within your vps which is beyond our support scope.
Vpses, in most cases, will always use a bridged network.
If you have added normal ip pool with routed option on/off then make sure viifbr0 or any other default bridge is started or not.
To start virtnetwork (bridge as a service) you can check this guide :
And to create it as a permanent Linux bridge then you can use this guide :
You can view the created bridge using :
If you have added VLAN, Internal or NAT ip pool on panel then check if corresponding bridge is setup properly and working as expected.
Previous command will help you check if the bridge is attached to required network interface on server and also to vps interfaces.
If the vps interfaces are not attached to the bridge then you can either stop and start vps from panel or try attaching it manually :
brctl addif viifbr0 viifv1001
Where viifv1001 is vps interface and viifbr0 is your bridge name.