I'm having problems getting the frontend to work over ssl. I have verified that it starts and runs with ssl: false on port 4000. I have added valid .key and .pem files to config/ssl and simply changed ssl to true, rebuilt, and started via pm2
The build completes without an error, and dspace-angular starts without error as well (specifically, I do not get the error I observed when I accidentally loaded a wrong .pem file). My .pm2/logs/dspace-angular-out.log is: yarn run v1.16.0 $ node dist/server [13:03:03 GMT-0500 (Central Daylight Time)] Listening at https:// <myfrontend>.edu:4000/ and my .pm2/logs/dspace-angular-error.log is empty However, when I try to connect via the url given in the log file, I get no response, and the browser or curl simply hangs. The error log remains empty, and the out log has an additional entry: [HPM] Proxy created: / -> https://<mybackend>.edu/server/sitemaps Again, this all works OK with ssl: false and no other changes. Any clue as to what I may have done wrong? Thank you, ~~ Bill -- Human wheels spin round and round While the clock keeps the pace... -- John Mellencamp ________________________________________________________________ Bill Tantzen University of Minnesota Libraries 612-626-9949 (U of M) 612-325-1777 (cell) -- All messages to this mailing list should adhere to the Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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/CADgrb7Gaf-nCwb78UHVkOKvtT7WenU5Uamzz7YyAFKJqibYfaQ%40mail.gmail.com.
