Skip to main content
Solved

How to disable https in Virtual Lab Router?

  • May 12, 2025
  • 4 comments
  • 32 views

Forum|alt.badge.img+1

Recently found out that the Virtual Router’s port 443 is open. 

PS C:\WINDOWS\system32> Test-NetConnection -ComputerName 10.3.14.205 -Port 443


ComputerName     : 10.y.y.y
RemoteAddress    : 10.y.y.y
RemotePort       : 443
InterfaceAlias   : _something.net
SourceAddress    : 10.z.z.z
TcpTestSucceeded : True

 

I tried using systemctl and service commands to verify status. Both do not work in this strip down linux version.  

Appreciate suggestions on how to remove apache2 or prevent it from starting at boot.

 

Best answer by Chris.Childerhose

That port is required for Virtual Labs.  You cannot shut it off that I am aware of unless Support knows.

4 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 9587 comments
  • Answer
  • May 12, 2025

That port is required for Virtual Labs.  You cannot shut it off that I am aware of unless Support knows.


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • 4903 comments
  • May 12, 2025

The Proxy Appliance that gets deployed isn’t configurable.
https://helpcenter.veeam.com/docs/backup/vsphere/vlab_proxy_vm.html?ver=120

https://helpcenter.veeam.com/docs/backup/vsphere/surebackup_proxy_appliance.html?ver=120

If Support can’t help, maybe post a feature request for the Veeam PMs to add configurability to the Appliance in the Forums.

Best.


Forum|alt.badge.img+1
  • Author
  • Influencer
  • 100 comments
  • May 12, 2025

We only use the Virtual Router as a dummy device for our Orchestration testing since we are using a T1 router in VMWare NSX where all the isolated segments are connected. 

I will open a ticket with support re this issue. Thanks so  much for the feedback!


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 9587 comments
  • May 12, 2025

We only use the Virtual Router as a dummy device for our Orchestration testing since we are using a T1 router in VMWare NSX where all the isolated segments are connected. 

I will open a ticket with support re this issue. Thanks so  much for the feedback!

Best of luck and hopefully they have a workaround.