sorry, I have a beginner question, I don't quite understand what ip or url go in local.cfg and conf.prod.yml.can anyone explain me?.thanks for everything. El lunes, 10 de febrero de 2025 a la(s) 2:25:38 p.m. UTC-3, DSpace Community escribió:
> Hi, > > I'd highly recommend following the installation guide in the official > Documentation at > https://wiki.lyrasis.org/display/DSDOC8x/Installing+DSpace > > Specifically, there are guides in that document for how to enable HTTPS > support for production (see step 16 of the Backend installation and step 8 > of the Frontend installation). > > We highly recommend using a proxy (either Apache HTTPD or Nginx), as that > will make your entire configuration a *lot easier*...and you won't need to > run everything off of ports 8080 and 4000. You will also need to create > and install an SSL certificate in order to move to HTTPS. It's unclear if > you have done so, but again there are guidelines in the official > documentation. > > Tim > > On Monday, January 20, 2025 at 6:39:51 PM UTC-6 matheu...@gmail.com wrote: > >> Dear Team, >> >> I'm having a hard time trying to implement DSpace 8 for my >> university. So far, I've created this brief documentation of the current >> error. This is my first post here, so I'm really grateful for your >> attention and any comments you might have. >> >> Virtual Machine Configuration: >> >> - >> >> 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 >> - >> >> Test 01: Default Settings >> >> 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 HTTPS >> >> config.yml >> >> dspace.cfg >> >> test:rest >> >> resultado: >> >> observações: NDA >> >> -- 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 dspace-community+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/dspace-community/7cd55d29-4802-4c38-8a12-a7db4742bfb0n%40googlegroups.com.
