I get "Failed to Fetch" when I try to log in

Created by Steve Place, Modified on Tue, Jul 23 at 3:52 PM by Steve Place

General troubleshooting


The first troubleshooting step in this situation is to curl your endpoint:

curl -I -v https://[your endpoint]:[port]/admin/healthcheck 

The output should look something like this:

❯ curl -I -v http://[your endpoint]:[port]/admin/healthcheck
*   Trying [::1]:[port]...
* Connected to localhost (::1) port [port]
> HEAD /admin/healthcheck HTTP/1.1
> Host: [your endpoint]:[port]
> User-Agent: curl/8.4.0
> Accept: */*
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Connection: keep-alive
Connection: keep-alive
< Content-Length: 0
Content-Length: 0
< Date: [date]
Date: [date]

<
* Connection #0 to host [your endpoint] left intact

If you do not get an output like this, send the following in a support ticket:

  1. The output you do get from the above curl command
  2. The output from the browser console
  3. The .har file from the Network tab
    1. Before collecting this, make sure you have the Network tab open, refresh the page, and cause the "Failed to Fetch" error to occur again.
    2. For more detailed instructions on generating a .har file, see here.


A common source of error here is using self-signed certificates that your browser does not trust. The solution is to use a certificate from a certificate authority like Let's Encrypt and ensuring the entire certificate chain is in your truststore.


Kerberos


You may receive this error if you authenticate with Kerberos. To solve this, add https://cloud.stardog.com to cors.allowed.orgins in stardog.properties and restart your server. Read more here.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article