Page History

...

See the Troubleshoot an error guide, look for the section on "DSpace 7.x ( or above)8.x".  This will provide you hints on locating error messages both in the User Interface (frontend) and in the REST API (backend)

...

1. First, create a [dspace-ui-deploy]/config/config.dev.yml configuration file for development.  This file supports the same configs as your existing config.prod.yml.  So, you can copy over any settings you want to test out.

2. Start the UI in development mode (this doesn't require a proxy like Apache or Nginx)

   Code Block
   yarn start:dev

   
   

3. This will boot up the User Interface on whatever port you specified in "config.dev.yml"
4. At this point, attempt to access the UI from your web browser.  Even if it isn't fully working, you should be able to still get more information from your browser's DevTools regarding the underlying error.  See the Troubleshoot an error page, look for the section on "DSpace 7.x ( or above)8.x".  It has a guide for locating UI error messages in your browser's Developer Tools.

...

Chances are your User Interface (UI) is throwing an error or receiving an unexpected response from the REST API backend.  Since the UI is Javascript based, it runs entirely in your browser.  That means the error it's hitting is most easily viewed in your browser (and in fact the error may never appear in log files).  

See the Troubleshoot an error page, look for the section on "DSpace 7.x ( or above)8.x".  It has a guide for locating UI error messages in your browser's Developer Tools.

...

If none of the above suggestions helped, you may want to look closer at the request logs in your browser (using browser's Dev Tools) and server-side logs, to be sure that the requests from your UI are going where you expect, and see if they appear also on the backend.  Tips for finding these logs can be found in the "DSpace 7.x ( or above)8.x" section of our Troubleshoot an error guide.

...