You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: