running the frontend over ssl

[Bill Tantzen]

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)

[Bill Tantzen]

Still experimenting with this issue, and I have a little more info:  curl --verbose gives a few more details and everything looks OK...  My recollection is that this worked fine in previous betas.

curl --verbose https://<myfrontend>:4000/
Trying xxx.xxx.xxx.xxx...
* TCP_NODELAY set
* Connected to <myfrontend> (xxx.xxx.xxx.xxx) port 4000 (#0)

...

...

...

*  SSL certificate verify ok.
> GET / HTTP/1.1
> Host: <myfrontend>:4000
> User-Agent: curl/7.64.1
> Accept: */*
>

At this point, curl (like my browser) simply hangs.  There is nothing in the pm2 out.log nor in the error.log

[Tyler Mobley]

Did you ever resolve this? I'm having the same issue over Apache getting 7.0 up and running. PM2 log keeps mentioning the proxy created just as above.

[Tyler Mobley]

Just adding here I'm all good. This was caused in my case but a faulty Apache vhost and environment.ts configuration RE SSL for the frontend.