Eric
11/30/2020, 9:53 AMprefect.utilities.exceptions.ClientError: 400 Client Error: Bad Request for url: http://<Prefect Cloud IP>:4200
This is likely caused by a poorly formatted GraphQL query or mutation. GraphQL sent:
query {
query { auth_info { api_token_scope } }
}
variables {
null
}
Is there any missing step when I set Prefect agent? Thank you very much!Kyle Moon-Wright
11/30/2020, 4:45 PMprefect backend cloud
before starting you agent - prefect agent docker start -t <MY_TOKEN>
.
You can always switch back to poll your Server instance for work by issuing prefect backend server
before starting your agent and specifying a URL with the API flag.Eric
12/01/2020, 1:11 AMrequests.exceptions.SSLError: HTTPSConnectionPool(host='<http://api.prefect.io|api.prefect.io>', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:1076)')))
I can connect to cloud.prefect.io via curl -v <http://cloud.prefect.io|cloud.prefect.io>
but the agent still connot connect to my Prefect cloud 😥Kyle Moon-Wright
12/01/2020, 1:29 AMprefect backend cloud
where our Agent lives
3. Have a running Docker daemon for the Docker Agent to access
4. Provide a Runner token to the Agent to verify Agent auth
5. Run the Agent with the CLI and verify it’s hitting our instance of Cloud in the Agent tile
So it’s tough to discern where this error is coming from. I’d recommend starting small and trying a LocalAgent with a fresh Runner token against the Cloud backend api for any deterministic leads.Eric
12/01/2020, 2:46 AM