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

Unable to see clients - GET /server.pem HTTP/1.1" 404 #112

Open
ThandoToto opened this issue Dec 6, 2019 · 1 comment
Open

Unable to see clients - GET /server.pem HTTP/1.1" 404 #112

ThandoToto opened this issue Dec 6, 2019 · 1 comment

Comments

@ThandoToto
Copy link

Hi

I'm wondering why I get this issue when the different clients, windows and ubuntu 19.04 are able to make the the following request and get a 200 ok response:
request:
http://myserver:8080/api/users/me/notifications/pending/count
response body:
{ " count":0}

But the more important step when setting up the client does not work:
EBUG:2019-12-06 06:55:47,702 connectionpool:437] http://myserver:8080 "GET /server.pem HTTP/1.1" 404 232

Is my server supposed to have a file named "server.pem" somewhere? I searched the whole computer and this file does not exist.

Regards,
T

@mbushkov
Copy link
Collaborator

mbushkov commented Dec 6, 2019

GRR has 2 components responding to HTTP requests. One is AdminUI - and it is the one you're sending requests to. AdminUI is designed to be used by analysts, it's a web interface and an API endpoint to GRR. Another component is GRR Frontend. This one communicates with GRR clients. server.pem is served by the Frontend, not by AdminUI.

AdminUI and Frontend run as different processes on different ports. What setting do you have for "Frontend.bind_port" on the server or for "Client.server_urls" on clients? You should use the specified address/port to query the server.pem.

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

No branches or pull requests

2 participants