https://www.ory.sh/ logo
Join Slack
Powered by
<@U04UQ68083H> what is configured wrong so that I ...
# ory-copilot
l
@chilly-king-10285 what is configured wrong so that I get this error on return to from login
Copy code
{
  "id": "backend-error",
  "error": {
    "config": {
      "url": "<http://konto.example.ee/kratos/public/self-service/login/flows?id=0a01136c-6ece-41a7-a244-0b0e67489255>",
      "method": "get",
      "headers": {
        "Accept": "application/json, text/plain, */*",
        "Cookie": "REDACTED",
        "User-Agent": "axios/0.21.4"
      },
      "transformRequest": [
        null
      ],
      "transformResponse": [
        null
      ],
      "timeout": 0,
      "xsrfCookieName": "XSRF-TOKEN",
      "xsrfHeaderName": "X-XSRF-TOKEN",
      "maxContentLength": -1,
      "maxBodyLength": -1,
      "transitional": {
        "silentJSONParsing": true,
        "forcedJSONParsing": true,
        "clarifyTimeoutError": false
      }
    }
  }
}
c
A message from kapa.ai
The error message you're seeing seems to be a backend error when trying to fetch the login flow from Ory Kratos. The error doesn't provide specific details about what's wrong, but there are a few things you could check: 1. URL: Make sure the URL in the 
config.url
field is correct and accessible. The URL should point to your Ory Kratos instance's public endpoint for fetching login flows. In your case, it's 
<http://konto.example.ee/kratos/public/self-service/login/flows?id=0a01136c-6ece-41a7-a244-0b0e67489255>
. 2. Headers: Check if the headers are correctly set. The 
Accept
header should be set to 
application/json, text/plain, */*
and the 
Cookie
header should include the client's cookies when fetching the self-service flows ([source](https://www.ory.sh/docs/troubleshooting/csrf#accessing-apis-from-a-server-side-application)). 3. Flow ID: The flow ID in the URL (
0a01136c-6ece-41a7-a244-0b0e67489255
in your case) should be a valid ID of an existing login flow. If the flow ID is incorrect or the flow has expired, you might get an error. If you've checked all these and you're still getting the error, it might be helpful to look at the server logs for more detailed error messages.
10 Views
Open in Slack
PreviousNext
Powered by