Hello, Many thanks. Now is working but I don't understand which was the problem? Can you explain to me ?
Thanks, Andrei Pe marți, 1 februarie 2022, la 10:38:32 UTC+2, [email protected] a scris: > Hello Andrei, > > I think you got it confused here by setting up the self signed certificate > and using the IP address to access your server ( What did you choose for > the common name of your self signed certificate? - The IP address? it can > be but usually the servers names not the IP addresses ). Anyway, I'll > assume you just wanted to run DSpace for development/testing reasons and > you don't need or want to worry about the apache/reverse proxy and the ssl > configurations. if my assumption is right then all you need to get DSpace > backend and the frontend up and running and accessible locally or remotely > is to shutdown the Apache webserver and make sure tomcat is running on port > 8080 and it did start the DSpace server Webapp and both ports 8080 and 4200 > you opted to run tomcat and frontend on are opened in the firewall and then > just changed the setting of the configuration files as you see them below. > > In the environment.prod.ts: > ui: { > ssl: false, > host: '10.0.0.234', > port: 4200, > nameSpace: '/' > }, > rest:{ > ssl: false, > host: '10.0.0.234', > port: 8080, > nameSpace: '/server' > }, > > In the local.cfg: > dspace.server.url = http://10.0.0.234:8080/server > dspace.ui.url = http://10.0.0.234:4200 > > > To access the backend from the browser type: http://10.0.0.234:8080/server > To access the frontend from the browser type: http://10.0.0.234:4200 > > NB: For the self signed certificate to work you have to have your own > Certificate Authority to sign your self signed certificate and you have to > add the public CA certificate as a trusted root certificate in both the > server where the apache is installed and on the client machine where you > will be accessing the apache or the dspace frontend. The other options you > have is to use letsencrypt or buy a commercial one. > On Monday, January 31, 2022 at 11:15:59 PM UTC+3 [email protected] > wrote: > >> Hello, >> I installed REST API and UI on a development VM which has the IP >> 10.0.0.234. >> The REST is configured on ssl. >> I'm unable to log-in in the UI when I'm accessing the UI from another >> host . In Developer Tools I can see the following error (error1.png): >> [image: error1.PNG] >> I don't know where is the mistake. >> The environment.prod.ts looks like this: >> ui: { >> ssl: false, >> host: '10.0.0.234', >> port: 4200, >> nameSpace: '/' >> }, >> rest:{ >> ssl: true, >> host: '10.0.0.234', >> port: 443, >> nameSpace: '/server' >> }, >> >> The local.cfg looks like this: >> dspace.server.url=https://10.0.0.234/server >> dspace.ui.url=http://10.0.0.234:4200 >> rest.cors.allowed-origins = ${dspace.ui.url} >> >> P.S. >> I tried the login from the VM where dspace REST and UI are running and >> the UI remains ,,loading state,, (only the points are being shown). Please >> see the attached picture (error2.png): >> [image: error2.PNG] >> >> Thanks, >> Andrei >> >> -- 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 on the web visit https://groups.google.com/d/msgid/dspace-tech/ae311197-46aa-4070-8019-004dc8e18ab4n%40googlegroups.com.
