Memory: 12.00GB
Processors: 6 (1 socket, 6 cores)
BIOS: Default (SeaBIOS)
Machine: Default (1440fx)
SCSI Controller: VirtIO SCSI
ISO: Ubuntu_Desktop_22.04.iso
DSpace Version: DSpace 8.0 Back-End/Front-End
Yarn Version: 1.22.22
Node Version: 18.13.0
config.yml
dspace.cfg
test:rest
Result:
Both the back-end and front-end function normally, but without HTTPS.
Test 02: Changing the REST URL to the URL
config.yml
dspace.cfg
test:rest
Result:
The UI does not load correctly.
Upon removing ":4000" from dspace.cfg, the issue persists.
Observations:
We noticed that during testing, ":8080" is allocated in the URL to access the server, which creates potential redundancy, as the server is running normally at the correct URL.
Test 03: Changing the REST URL to HTTPS
Result: The same results as the previous test. Even after changing dspace.cfg to HTTPS, the test connection continues to show HTTP. (If SSL is activated, it uses HTTPS.)
Test 04: UI on the URL and REST on the IP
test:rest:
Resultado:
While investigating "200.137.5.231," I decided to revert to a snapshot for testing. The error persists, but with the machine's previous IP address. I attempted to use lsof to stop old processes on the port, but without success.
antigo na porta, mas nao obtive sucesso
Sources about the error:
https://groups.google.com/g/dspace-tech/c/O2nvMaAbOjk
I tested the solution from this thread, but it was not effective.
Test 05: UI and REST on the URL with HTTPSconfig.yml
dspace.cfg
test:rest
resultado:
observações: NDA