I'm using the Node Js (Debian 8) Bitnami install on Google Compute Engine. I have installed a custom Node Js Express application, and am trying to access it via SSL. I have a DNS A record pointing the appropriate subdomain to my server's public IP address. Everything works fine if I use the "app-prefix" method, but "https" fails. I have switched to "app-vhosts" thinking I need to define separate settings to ports 80 and 443. I have a valid certificate and ca-bundle from GoDaddy on the server now (in apache2/conf), which I named "server.crt" and "server-ca.crt" (the defaults). I also updated apache2/conf/bitnami/bitnami-apps-vhosts.conf to include "/opt/bitnami/apps/[myapp]/conf/httpd-vhosts.conf". The contents of that app vhosts file is:
MY PROBLEM: I can get to my application successfully without "https" protocol. If I go to "https://api.myapp.com", I get a certificate error. If I look at the details for the error in Chrome, I see that it is still serving the default "www.example.com" certificate! If I go to "https://[my.ip.address]", I get a similar error, but this time it is trying to serve my correct GoDaddy certificate. I need that custom certificate to be associated with my virtual host. Please help!