Broker VM connection issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Broker VM connection issue

L2 Linker

Hi Community

 

We're facing an connection issue with Endpoints using Broker VMs (agent proxy). We opened a TAC case, but it's stuck. There is no useful help yet.

- Endpoints are isolated from the internet (no direct or webproxy access)
- Endpoints are registered in Cortex, but doesn't get content updates
- Live terminal to endpoints is not possible
- Brokers connect to the internet through a webproxy
- Webproxy has whitelisted the URLs* (no Authentication, no TLS Interception)

 

We've checked the following:
- Re-installed agents
- Re-deployed brokers
- Connection from endpoints to brokers is successful (tcp8888)
- Connection from brokers to URLs* is successful (https)

 

Has anyone some useful information or connectivity tests we can run?

 

*) https://docs-cortex.paloaltonetworks.com/r/Cortex-XDR/Cortex-XDR-Pro-Administrator-Guide/Resources-R...

 

Thanks & Best regards

1 accepted solution

Accepted Solutions

L2 Linker

Hi Community

 

Finally we figured out what caused this issue!


The brokers transmits all HTTP packets to the webproxy with the endpoints IP addresses as source.
So the webproxy blocked the connections as we only add the brokers IP addresses on the URL whitelist.

We mainly focused on connections between the brokers and webproxy/internet. However, because webproxy rules apply on application layer, we overlooked this.

 

After activating content caching on the brokers (and tcp443 connections) everything works fine.

 

Best regards

View solution in original post

2 REPLIES 2

L4 Transporter

Hello Roman,

We have not came across such scenarios. This case requires TAC intervention.

 

If it is stuck, I would suggest reaching out to Accounts Team to accelerate the progress.

 

Thanks!

 

 

Ashutosh Patil

L2 Linker

Hi Community

 

Finally we figured out what caused this issue!


The brokers transmits all HTTP packets to the webproxy with the endpoints IP addresses as source.
So the webproxy blocked the connections as we only add the brokers IP addresses on the URL whitelist.

We mainly focused on connections between the brokers and webproxy/internet. However, because webproxy rules apply on application layer, we overlooked this.

 

After activating content caching on the brokers (and tcp443 connections) everything works fine.

 

Best regards

  • 1 accepted solution
  • 1695 Views
  • 2 replies
  • 0 Likes
  • 78 Subscriptions
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!