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.

Sign up for GitHub

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

Jump to bottom

Client err="malformed HTTP request \"<html>\"" #77

Open
denibertovic opened this issue Apr 8, 2020 · 5 comments
Open

Client err="malformed HTTP request \"<html>\"" #77

denibertovic opened this issue Apr 8, 2020 · 5 comments

Comments

@denibertovic
Copy link

I'm trying to run pushprox but I'm getting the following error:

caller=main.go:179 msg="Error reading request:" err="malformed HTTP request """

My setup is ALB (http->https redirect) -> Nginx (basic auth) -> pushprox-proxy.
The clients however are on HTTP only.

Since I figured it might be something to do with mixing https and http I got rid of 301 redirect to https and tried serving and connecting to the proxy over HTTP. I also tried getting rid of the Nginx in font that was providing basic auth but the problem remained the same.

This appears to be the only errors I'm seeing. The proxy doesn't appear to be outputting any errors.
And of course no metrics are being scraped.
@denibertovic
Copy link
Author

A bit of an update. It would seem that it's the ALBs fault somehow. If I use the EC2 instance directly then it works.

Interesting side realization btw....the node was marked as UP the entire time even though no scrapes were happening.

@scythargon
Copy link

Hi! Have you figured out what was the issue? I'm experiencing a very similar problem.

pushprox-client is outputting err="malformed HTTP request \"\"" error, is shown live, but no scrapes are successful.

@walkure walkure mentioned this issue Jan 23, 2023
Open
@hendras8
Copy link

any updates on this case? because I am experiencing the same thing. it seems to be wrong in the request from pushprox-client, because in Prometheus and nginx it's already correct.

@denibertovic
Copy link
Author

I haven't figured out the issue that happened and I ended up not using this project. Took a different approach. Feel free to close.

@menvol3
Copy link

menvol3 commented Mar 19, 2024

I faced the same issue. Does anyone know how to resolve it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@denibertovic @scythargon @menvol3 @hendras8