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

Patchman server returns 400 Bad Request #587

Open
viktordw opened this issue May 22, 2024 · 1 comment
Open

Patchman server returns 400 Bad Request #587

viktordw opened this issue May 22, 2024 · 1 comment
Labels

Comments

@viktordw
Copy link

Hello,

I installed Patchman server and client as described in INSTALL.md, and I successfully added the monitoring of local server packages by running patchman-client -s http://127.0.0.1/patchman command on server.

The public IPv4 address of the client is added in Require IP directive inside the apache Location block, and on client machine, the client address is added to the ALLOWED_HOSTS list, inside /etc/patchman/local_settings.py file.

After running patchman-client -v -s http://example.com/patchman (i have registered domain, just have replaced it with example.com after pasting it), near the end of the output from CURL, the response from server is the following:

HTTP/1.1 400 Bad Request
Date: Wed, 22 May 2024 12:15:35 GMT
Server: Apache/2.4.52 (Ubuntu)
X-Content-Type-Options: nosniff
Referrer-Policy: same-origin
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html


<!doctype html>
<html lang="en">
<head>
  <title>Bad Request (400)</title>
</head>
<body>
  <h1>Bad Request (400)</h1><p></p>
</body>
</html>

@furlongm do you have any idea what might be causing the issue?

@furlongm
Copy link
Owner

Check the apache logs, but I think require ip is the ip range of the clients. The apache logs should let you know if this is the case.

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