Accessing dspace 8 UI on LAN on ubuntu server

[Wanangwa Nyirenda]

Hello there professional users, I am having a hard time accessing my dspace 8 UI on my LAN Even though I was able to before along with all my staff on the LAN by using the IP http://192.168.1.211:4000 . I was trying to change up my friend end a little then all of a sudden no one can access the page. When I run yarn start from my dspace-angular directory I get the following output   

     

Environment extended with app config

dspace-angular
Version: 8.0.0
Environment: Production

[HPM] Proxy created: /  -> http://localhost:8080/server/sitemaps
[HPM] Proxy created: /  -> http://localhost:8080/server
[14:34:56 GMT+0300 (East Africa Time)] Listening at http://localhost:4000/

which I believe should show me the dspace homepage but instead the homepage appears for only a second and the shows the 500 service unavailable error.I run all the diagnostics and made sure both my frontend and backend are fine and even restarted all my services like solr, tomcat and postgres. From what I have been able to find out my checking the diagnostics page for the 500 error(common fixes for 500 error) the problem is likely bad communication between the backend and UI. Here is how my configurations are looking;

local.cfg

dspace.dir=/dspace
dspace.server.url = http://192.168.1.211:8080/server
dspace.ui.url = http://192.168.1.211:4000
dspace.name = DSpace at My University

db.url = jdbc:postgresql://localhost:5432/dspace

db.username = dspace
db.password = dspace

ldn.enabled = true
rest.cors.allowed-origins = http://192.168.1.211:4000

config.yml

rest:
  ssl: false
  host: localhost
  port: 8080
  nameSpace: /server

And when I run   yarn test:rest  it returns this output;

yarn run v1.22.22
$ 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 8.0
"dspaceUI" = http://192.168.1.211:4000
"dspaceServer" = http://192.168.1.211:8080/server
"dspaceServer" property matches UI's "rest" config? false
Does "/api" endpoint have HAL links ("_links" section)? true

I have been stuck trying to fix this since last week and I'm at a loss for what to do. Before you just refer me to the page talking about the common fixes to the 500 error I have tried each of the suggested solutions thoroughly before coming here. Any assistance would be greatly appreciated.

Kind regards,

Wanangwa.