Page History

...

This error means that the UI is unable to contact the REST API listed at [rest-api-url] and/or the response from that [rest-api-url] is unexpected (as it doesn't contain the "_links" to the endpoints available at that REST API).  A valid DSpace [rest-api-url] will respond with JSON similar to our demo API at https://api7.dspace.org/server/api

Unfortunately, this is a generic error message which simply says your frontend cannot communicate with your backend.  It may be caused by a variety of installation scenarios...these are a few we've discovered so far:

• A possible configuration issue in the frontend or backend.
  • Check the "rest" section of your environment.*.ts configuration file for the User Interface.  That configuration section defines which REST API the UI will attempt to use.  If the settings do NOT map to a valid DSpace REST API, then you will see this "No _links section found.." error.
  • Check the "dspace.ui.url" configuration of your backend & verify it corresponds to the public URL of the User Interface (i.e. the exact same URL you use in your browser)
• A possible SSL certificate issue. This issue may also appear if the REST API's SSL Certificate is either untrusted (by the frontend) or expired.  See also "Using a Self-Signed SSL Certificate causes the Frontend to not be able to access the Backend" common issue listed below.
• Something blocking access to the REST API. This may be a proxy issue, a firewall issue, or something else generally blocking the port (e.g. port 443 for SSL).
  • Verify that you can access the REST API from the machine where Node.js is running (i.e. your UI is running).  For example try a simple "curlwget" or "wgetcurl" to verify the REST API is returning expected JSON similar to our demo API at https://api7.dspace.org/server/api

    
    

    Code Block
    # Attempt to access the REST API via HTTPS from command-line # on the machine where Node.js is running. # If this fails or throws a SSL cert error, you must fix it. wget https://[rest.host]/server/api

    
    

  • In most production scenarios, your REST API should be publicly accessible on the web, unless you are guaranteed that all your DSpace users will access the site behind a VPN or similar.  So, this "No _links section found" error may also occur if you are accessing the UI from a client computer/web browser which is unable to access the REST API.

...