Hi Vahe, It is tricky for sure. Recently I put up my sample working http-based configuration in this email trail here: Setting up DSpace on Windows Server 2022 (google.com) <https://groups.google.com/g/dspace-tech/c/iLqVN87ovLI/m/Ev6wNMYFAgAJ?hl=en> Hopefully that will help! You will want to make sure that the values in your config.yml match what is in your local.cfg, even the port. Note that it is possible to comment out port in local.cfg and you may have to do that to get it to match up with config.yml.
I also had issues running PM2 from a separate deploy folder, getting CORS errors. I only had success with PM2 when my .json file was in the root of my install/build folder (/opt/dspace-7-angular, for me). Also note that the naming of environment variables seems to have changed for version 7.6.1 of Dspace. Check the documentation to be sure. I'd also say, before trying to get things working with PM2, try ensuring that they work with yarn (yarn start, yarn test:rest). Also, I couldn't get self-signed certs to work at all, not even with the NODE_EXTRA_CA_CERTS, so be sure that when you switch to HTTPS that you have a truly valid cert from a recognized CA. That is what I've deduced so far, and I'm willing to be wrong on things... Best, Katy On Thursday, November 30, 2023 at 6:15:02 AM UTC-8 Vahe Ghorghorian wrote: > If anyone please at least can give a hint ???? much appreciated ! i > reverted back and removed the HTTPS. and using HTTP with the domain name > the application opens ,i go to Login page and put the correct credentails > and the page loads and loads and loads without bringing anything ....what > could be the error ? > > On Thursday, November 30, 2023 at 8:09:47 AM UTC+2 Vahe Ghorghorian wrote: > >> *in local.cfg i am using * >> dspace.server.url = https://HaigRepository.haigazian.edu.lb/server >> dspace.ui.url = https://HaigRepository.haigazian.edu.lb >> dspace.ui.url = https://192.168.4.4 >> rest.cors.allowed-origins = ${dspace.ui.url} , http://localhost:4000 >> *in config.yml* >> ui: >> ssl: false >> host: localhost >> port: 4000 >> nameSpace: / >> useProxies: true >> >> # The REST API server settings >> # NOTE: these settings define which (publicly available) REST API to use. >> They are usually >> # 'synced' with the 'dspace.server.url' setting in your backend's >> local.cfg. >> rest: >> ssl: true >> host: HaigRepository.haigazian.edu.lb >> port: 443 >> # NOTE: Space is capitalized because 'namespace' is a reserved string >> in TypeScript >> nameSpace: /server >> >> *in the json file * >> "env": { >> "NODE_ENV": "production", >> "DSPACE_REST_HOST": "HaigRepository.haigazian.edu.lb", >> "DSPACE_REST_SSL": "true", >> "DSPACE_REST_PORT": "443", >> "DSPACE_REST_NAMESPACE": "/server" >> } >> >> anything missing please advise. >> On Wednesday, November 29, 2023 at 6:57:27 PM UTC+2 Vahe Ghorghorian >> wrote: >> >>> I have just installed dspace 7 on a windows 10 machine. Moreover i have >>> installed a certificate as well.when i put the domain name the page is >>> opening normally and if i browse all the links it opens, now when i log in >>> if i put incorrect password it says invalid, but if i put correct one, it >>> should take me to the page where i add community, items etc... Admin site >>> that is.but the page keeps on loading and loading as if something is >>> blocking it and than gives the error attached. Im stuck here and i need >>> help already the installation and the certificate took a lot of time and i >>> reached to thia stage i need ot fixed please. >>> The tomcat also in the logs its giving this error. >>> [proxy_http:error] [pid 7644:tid 1216] (os 10060)a connection attempt >>> failed because the connected party did not properly respond after a period >>> of time, or established connection failed because connected host has failed >>> to respond. : [client 192.168.4.4:52293] ah01102: error reading status >>> line from remote server localhost:4000, referer: (domain name) please help >>> >> -- 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 dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/a8be702b-547c-4e6b-a163-95522e695884n%40googlegroups.com.
