Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Occasionally getting the 502 Proxy error while running this clamscan service on the Prod server. #85

Open
reshmpk1 opened this issue Jan 19, 2022 · 3 comments
Labels

Comments

@reshmpk1
Copy link

reshmpk1 commented Jan 19, 2022

I am getting this below mentioned error some times on our stage and production server:

<title>502 Proxy Error</title>

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request

Reason: Error reading from remote server

We have load balance and multiple app servers behind our VM host.
NOTE: Looking for your valuable input on this issue

@kylefarris
Copy link
Owner

It's hard to help you without a better idea of how you have everything setup, your network/server topology, etc... I'll help if I can but I need more info.

@reshmpk1
Copy link
Author

reshmpk1 commented Feb 15, 2022

https://javascript.plainenglish.io/integrate-clamav-antivirus-software-in-your-node-js-application-39d92ff76792
These are the steps we followed to integrate the clamscan.
configured the clamscan and camdscan objects, initialing the Clamscan with the file path and applying the scanning a file that is attached.

We have Akamai proxy in front of the LB and behind the LB 2 VMs.

image

@kylefarris
Copy link
Owner

kylefarris commented Feb 15, 2022

You have two proxies. The Akamai one and the Apache one. Do you know which proxy is having the issue? What kind of requests are you making? You're running a node server obviously, so, are you able to hit any endpoints on that service? Maybe just a basic "Hello World" endpoint? If that doesn't work, then this is outside the scope of this project. If it's only happening on endpoints involving this library, I'll need some more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants