- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
11-14-2024 02:05 AM
Hello Team,
We have configured the Palo Alto firewall as an Explicit Proxy using Kerberos authentication in alignment with the Admin Guide. However, we’re noticing that the designated traffic is not routing through the Proxy as expected and is failing to initiate from the Proxy-Zone to the Internet-Zone.
When attempting to access a webpage from a user’s device, we’re encountering the following error: "upstream connect error or disconnect/reset before headers, reset reason: connection failure."
Could someone provide guidance on troubleshooting this issue? Insights on potential configuration aspects or logs to review would be greatly appreciated.
Thanks
11-14-2024 08:14 AM
I'm literally setting this up for a client now, first time!
I have the same issues as you've seen. I expect the interfaces for the proxy all need to be in a dedicated VR with the default route routing via the 'external' proxy network (therefore forcing it out of that interface/zone).
11-16-2024 08:32 PM
Hello,
As per the documentation, the interfaces should be within the same virtual routers and the same virtual systems.
Do update, if you were able to make it work.
01-06-2025 01:07 PM
Did you ever figure this out? I am having the same issue.
01-29-2025 09:32 PM
Anything on this -- observing the same
05-29-2025 05:39 AM
Hi Kalpesh,
I'm also trying to configure it on the Palo Alto firewall and I am struggling with the config: did you use a loopback interface for the incoming traffic or you used an external interface you have configured on the firewall? Also, for the DNS proxy config, have you selected your external interface/loopback or the internal? I have read different articles and everyone has their own of doing it.
05-29-2025 05:53 AM
We used the steps mentioned in below document from palo alto:
Recalling, we had run below powershell command, to invoke a web request and to authenticate the same and it trigerred to resolve the issue,
Basic Proxy Usage:
$proxy = "http://proxyserver:8080"
$response = Invoke-WebRequest -Uri "http://example.com" -Proxy $proxy
Write-Output $response.Content
Proxy with Credentials:
$proxy = "http://proxyserver:8080"
$proxyCredentials = Get-Credential
$response = Invoke-WebRequest -Uri "http://example.com" -Proxy $proxy -ProxyCredential $proxyCredentials
Write-Output $response.Content
Hope it helps!
05-29-2025 09:03 AM
Thank you for this. I am following the same article you shared, however I am struggling with these bits:
For me, based on the doc, the upstream interface and the DNS proxy zone interface are the same: loopback 1. The confusing bit is that I thought the loopback interface should be only used for DNS resolution and incoming traffic from the Internet.
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!