cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Not applicable
Report Inappropriate Content
Message 1 of 2

502 Proxy error: Proxy server could not handle the request post/psp/api

when we enable “client IP & x-forward-for” so our Netscaler VIP forwards the client IP’s to the proxy, we receive a proxy error. Please see the image attached. Proxy Error: The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST/PSP/api/1.0/checkout Reason: Error reading from remote server. URL: psp-psm.testservicensw.net/PSP/api/1.0/checkout
1 Reply
McAfee Employee mkutrieba
McAfee Employee
Report Inappropriate Content
Message 2 of 2

Re: 502 Proxy error: Proxy server could not handle the request post/psp/api

Hi,

 

unfortunately, I cannot see a screenshot attached but anyway, I would recommend to open a Service Request and create/attach the following debug data + exact client IP and URL to it (config and connection need to be checked from technical side, please do not upload such personal data here in the public community😞

FEEDBACK FILE
To create a feedback file, navigate to "Troubleshooting" > "Feedback". Then click the "Create Feedback File" button. This provides us with your configuration as well as debug information to help troubleshoot any issues you may be experiencing.

Via CLI:
/opt/mwg/bin/feedback.sh -l 2

RULE TRACE
Please navigate to "Troubleshooting" > "Rule tracing central". Enter the client IP you are testing with. Press the "Go" button and reproduce the issue. Afterwards, press the "Stop" button and export all visible traces.

TCPDUMP
1) Navigate to Troubleshooting > Packet Tracing
2) Enter the following parameter: -npi any -s 0
If you know all IP addresses: -npi any -s 0 host <clientIP> or host <destinationIP>
3) Start the tcpdump
4) Reproduce the issue
5) Stop the tcpdump
6) Click on Download, zip the tcpdump file and send to us

IMPORTANT: Please tell us the IP addresses used (Client IP, Proxy IP, URL)

CONNECTION TRACING
1) Navigate to “Configuration” > “Troubleshooting”
2) Enable “Enable connection tracing”
3) Enable “Restrict connection tracing to one IP”
4) Enter the client IP you are testing with
5) Save the changes
6) Reproduce the issue
7) Disable "Enable connection tracing"

Please provide all the text files you find under "Troubleshooting" > "Connection tracing".

To collect the files using SSH:
cd /opt/mwg/log/debug/
zip {{SR}}_conntraces.zip connection_tracing/*

 

Regards,
Marcel

Regards,
Marcel Kutrieba
Technical Support Engineer
More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator
  • Community Help Hub

      New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

    • Find Forum FAQs
    • Learn How to Earn Badges
    • Ask for Help
    Go to Community Help

    Join the Community

      Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

    • Get helpful solutions from McAfee experts.
    • Stay connected to product conversations that matter to you.
    • Participate in product groups led by McAfee employees.
    Join the Community
    Join the Community