New installation DSpace 9.2 - 500 Service unavailable

[Martin Volný]

Hello DSpace community,
I’m reaching out with a question about installation DSpace 9.2 and troubleshooting an issue.
This is our test environment and my first time practical experience, so I apologize in advance for any trivial mistake I may have missed.
We have DSpace in version 9.2, where are hosted backend and frontend on the same server. We are not not using HTTPS.
When I will open user Interface, web pages are showing, but a few second later it is redirect to error message 500
Error message:
"500 Service unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
I cannot log in to the system; only the DSpace language locale can be changed.
I checked possible problems on wiki webpages, but I received from console 200.

REST API from the UI from the command-line
npm run test:rest

ubuntu@dm4ai-test:/opt/dspace-angular$ npm run test:rest

> dspace-...@9.2.0 test:rest
> ts-node --project ./tsconfig.ts-node.json scripts/test-rest.ts

Building production app config
Overriding app config with /opt/dspace-angular/config/config.yml
Unable to find env config file at /opt/dspace-angular/config/config.production.yaml
...Testing connection to REST API at http://localhost:8080/server/api...

RESPONSE: 200

Checking JSON returned for validity...
        "dspaceVersion" = DSpace 9.2
        "dspaceUI" = http://localhost:4000
        "dspaceServer" = http://localhost:8080/server
        "dspaceServer" property matches UI's "rest" config? true
        Does "/api" endpoint have HAL links ("_links" section)? true
ubuntu@dm4ai-test:/opt/dspace-angular$

Server Api is accesible
http://localhost:8080/server/api

http://localhost:8983/solr/#/ is also ok
In developer tools is error message:

 

Thank you for any advice and tips on what I should check next and where to look.

[Kevon Muhoozi]

Dear Martin!

In the attached dev-tools in the browser, this means that the service is not reached by your front end, or it is your web server configurations blocking the access.
What web server are you currently using on your dev server?

--
All messages to this mailing list should adhere to the Code of Conduct: https://lyrasis.org/code-of-conduct/
---
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 dspace-tech...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/c1519b0b-274a-4638-9055-7c76c60b5807n%40googlegroups.com.

[Martin Volný]

Hello,
Thankx for quick response, As web server I have installed Apache Tomcat/10.1.55.
For additional information
OS: "Ubuntu 24.04.4 LTS"
Java: openjdk version "17.0.19" 2026-04-21
Solr: 9.10.1

Dne čtvrtek 18. června 2026 v 18:42:15 UTC+2 uživatel Kevon Muhoozi napsal:

[Victorhugo Bisangwa]

Hello Martin, Share your UI and Rest information of config.prod.yml and local.cfg

regards,

To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/65faf850-6d84-458f-a7f3-cbb01400ada8n%40googlegroups.com.

[Martin Volný]

Here are my settings for file: config.yml
ui:
  ssl: false
  host: 0.0.0.0 # Listen on all interfaces
  port: 4000

rest:
  ssl: false
  host: localhost
  port: 8080
  # NOTE: Space is capitalized because 'namespace' is a reserved string in TypeScript
  nameSpace: /server

And second file: local.cfg

dspace.server.url = http://localhost:8080/server
dspace.ui.url = http://localhost:4000
db.url = jdbc:postgresql://localhost:5432/dspace


rest.cors.allowed-origins = http://localhost:4000

Dne pátek 19. června 2026 v 11:54:39 UTC+2 uživatel Victorhugo Bisangwa napsal:

[Victorhugo Bisangwa]

From your first email; you mentioned this:

..Testing connection to REST API at http://localhost:8080/server/api...
RESPONSE: 200

So it looks like the backend is running.

From where are you opening the browser?  

• If the browser is running on another PC/laptop, then replace localhost in your configurations with your server hostname/IP.

Regards,

To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/1c5c52f8-79f3-4947-8161-75c7f61168e7n%40googlegroups.com.

[Martin Volný]

When I try to hit DSpace from web browser I´m able open web portal, i have possible change language. But a few second later I got error message 500.

Not sure, what I set wrongly.

Dne pátek 19. června 2026 v 13:39:01 UTC+2 uživatel Victorhugo Bisangwa napsal:

[Martin Volný]

Hello again,

So I tried to put IP address everywhere in configuration files. So it means local.cfg and also  config.yml. But no effect. Any Idea how I can continue with investigation. 
For overviwe you can hit my first test environment:

The Hal Browser:
http://195.113.175.153:8080/server/#/server/api
Solr Admin Console:
http://195.113.175.153:8983/solr/#/
And Frontend:
http://195.113.175.153:4000/500

Dne pátek 19. června 2026 v 13:53:49 UTC+2 uživatel Martin Volný napsal:

[Victorhugo Bisangwa]

Hello,

I checked the DSpace REST API through the HAL Browser and can confirm that the backend is running correctly and responding with HTTP 200. The frontend is currently not accessible. 

However, the API root currently reports:

"dspaceUI": "http://localhost:4000",
"dspaceServer": "http://localhost:8080/server"

This indicates that DSpace is still configured with localhost URLs.

While this does not prevent access to the backend via the server IP address, it can cause issues with frontend communication, authentication, redirects, generated links, and API integration when accessing DSpace from other machines.

Although the localhost configuration may not be the direct cause of the HTTP 500 error, it is not recommended for an externally accessible deployment and should be corrected before further troubleshooting. Once the URL configuration has been verified, we can continue investigating the frontend-side error.

       

To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/2eedf1f6-ed61-4d99-87e9-857ccfbaf64bn%40googlegroups.com.