Hi,

We have a guide for possible scenarios where this error may occur in our 
"Common Installation Issues".  See 
https://wiki.lyrasis.org/display/DSDOC8x/Installing+DSpace#InstallingDSpace-%22No_linkssectionfoundat...%22errorfromUserInterface

You also may want to use the troubleshooting guide to see if more 
information about the error can be found in your web browser's DevTools: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

On Tuesday, November 19, 2024 at 5:57:26 AM UTC-6 [email protected] wrote:

> Dear Team,
>
> I have successfully installed DSpace 8 and configured SSL. The software 
> was working fine for 4–5 days, but after that, the frontend page started 
> showing a 500 error.
>
> I checked the backend, tomcat, Solr, and Apache2 services, and they all 
> appear to be functioning properly. However, upon reviewing the frontend 
> logs, the following error is repeatedly displayed:
>
> No _links section found at https://library.bmu.edu.in/server/api  
> 0|dspace-8-angular | No _links section found at 
> https://library.bmu.edu.in/server/api
>
> *Note:- *When we configure DSpace on a local ip address, we update all 
> configuration files to use the local IP address and run build:prod. Once 
> that is done, we replace the configurations with the domain settings and 
> run build:prod again. After this process, DSpace works fine for a few days.
>
> However, after 4 days, the frontend starts showing a 500 error again. The 
> issue seems to recur despite the corrections.
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/dspace-community/19cf3195-0967-4355-9945-7054f2642c2fn%40googlegroups.com.

Reply via email to