Hi Anand, Could you please provide the entire Stacktrace, along with the 5-10 log lines just before this? The stacktrace you've provided only gives partial information. It seems to be saying your browse indexes are invalid, but it doesn't give a reason why.
It'd also be important to understand if this occurs on *every* browse/search page, or just some pages? If it's every page, it might be a problem with your Solr index or similar. So, you should try to run "./dspace index-discovery -b" from the commandline (to attempt to rebuild your indexes) and see if that succeeds or fails. If it fails, it might give more information as to why Solr isn't working. You should also look for any additional "ERROR" messages in your logs. Sometimes there are earlier "ERROR" messages that provide more details as to the problem, and they are the cause of the later ERROR messages. Tim On Friday, July 18, 2025 at 12:37:12 AM UTC-5 [email protected] wrote: > Hi Tim, > > Thank you for your reply, > > As you have said I have checked the dspace backend logs and i have found > this error: > > ERROR unknown 992914b9-aa89-4152-a3b0-458411a51f44 > org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ An > exception has occurred (status:500) java.lang.IllegalStateException: The > requested browse doesn't provide direct access to items you must specify a > filter at > org.dspace.app.rest.repository.BrowseItemLinkRepository.listBrowseItems(BrowseItemLinkRepository.java:82) > > at jdk.internal.reflect.GeneratedMethodAccessor518.invoke(Unknown Source) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at java.base/java.lang.reflect.Method.invoke(Method.java:569) ... (and the > rest of the stack trace) > > How do i fix this error or do i have to rebuild the package and install it > again or go to the next DSpace version whichis 8.2? > Anand > > On Wednesday, 16 July 2025 at 22:01:30 UTC+5:30 DSpace Technical Support > wrote: > >> Hi Anand, >> >> The logs you shared seem to be from the frontend, but the 500 Internal >> Server Error is usually thrown by the *backend*. I'd recommend looking for >> more details on the 500 error in your backend logs. See our >> Troubleshooting Guide for details: >> >> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove) >> >> The issue you shared on the frontend may be unrelated. It sounds like >> this issue https://github.com/DSpace/dspace-angular/issues/2315 , but >> it's usually harmless. There is a possible workaround in the comments on >> that ticket though. >> >> Tim >> On Monday, July 14, 2025 at 4:33:09 AM UTC-5 [email protected] wrote: >> >>> Dear DSpace Team, >>> >>> We’re facing a persistent issue with SSR in our DSpace 8.1 Angular UI >>> setup at https://ir.daiict.ac.in. >>> >>> Directly accessing or reloding pages like /community-list or /search >>> results in a 500 Internal Server Error. >>> >>> pm2 shows following error logs: >>> >>> /root/.pm2/logs/dspace-ui-error-1.log last 15 lines: >>> 1|dspace-u | at >>> /home/dspace/dspace-angular-dspace-8.1/dist/server/main.js:1:3736933 >>> 1|dspace-u | at _ZoneDelegate.invokeTask >>> (/home/dspace/dspace-angular-dspace-8.1/dist/server/main.js:1:3726815) >>> 1|dspace-u | at ZoneImpl2.runTask >>> (/home/dspace/dspace-angular-dspace-8.1/dist/server/main.js:1:3719213) >>> 1|dspace-u | Warning [ERR_HTTP_HEADERS_SENT]: Tried to set headers after >>> they were sent to the client >>> 1|dspace-u | Error: Cannot set headers after they are sent to the client >>> 1|dspace-u | at new NodeError (node:internal/errors:405:5) >>> 1|dspace-u | at ServerResponse.setHeader (node:_http_outgoing:648:11) >>> 1|dspace-u | at ServerResponse.res.set.res.header >>> (/home/dspace/dspace-angular-dspace-8.1/dist/server/main.js:1:2782438) >>> 1|dspace-u | at ServerResponse.res.send >>> (/home/dspace/dspace-angular-dspace-8.1/dist/server/main.js:1:2776806) >>> 1|dspace-u | at >>> /home/dspace/dspace-angular-dspace-8.1/dist/server/main.js:1:7636921 >>> 1|dspace-u | at _ZoneDelegate.invoke >>> (/home/dspace/dspace-angular-dspace-8.1/dist/server/main.js:1:3725973) >>> 1|dspace-u | at ZoneImpl2.run >>> (/home/dspace/dspace-angular-dspace-8.1/dist/server/main.js:1:3718144) >>> 1|dspace-u | at >>> /home/dspace/dspace-angular-dspace-8.1/dist/server/main.js:1:3736933 >>> 1|dspace-u | at _ZoneDelegate.invokeTask >>> (/home/dspace/dspace-angular-dspace-8.1/dist/server/main.js:1:3726815) >>> 1|dspace-u | at ZoneImpl2.runTask >>> (/home/dspace/dspace-angular-dspace-8.1/dist/server/main.js:1:3719213) >>> >>> Please help us in this regard, >>> >>> Best, >>> Anand >>> >> -- 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 Technical Support" 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-tech/20535d1b-b78c-4082-9300-d3738c8d4aefn%40googlegroups.com.
