Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
07-21-2024 10:56 PM
Hi Team,
I have a query regarding the installation of the Broker VM in our organization. We have successfully installed it internally. However, when we tried to access the URL https://<brokervm-ip>:4443 internally, it failed. After whitelisting the Palo Alto domain URLs, we were able to successfully access the URL https://<brokervm-ip>:4443 internally.
My question is: is it necessary to whitelist the Palo Alto domain URLs to access the URL https://<brokervm-ip>:4443 internally?
07-22-2024 05:14 AM
Hi @Vinothkumar_SBA, thanks for reaching us using the Live Community.
In our requirements doc about URLs and IPs to be enabled, the tenant URL is a requirement for the Borker VM. If the Broker doesn't reach the tenant, it doesn't know whar services are needed to be enabled.
If this post answers your question, please mark it as the solution.
07-22-2024 09:56 PM
Hi Jmazzeo,
Thank you for your response. However, we have disconnected the broker VM from the internet. We also tried accessing the URL https://<brokervm-ip>:4443 locally, and it successfully opened. How is this possible?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
