Keywords: Parse - AWS - Technical issue - Secure Connections (SSL/HTTPS)
bnsupport ID: 7092297b-cadf-c097-0d08-f740d94aff7d
? Apache: Found possible issues https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-errors-apache/ https://docs.bitnami.com/bch/apps/moodle/troubleshooting/deny-connections-bots-apache/
bndiagnostic failure reason: The suggested guides are not related with my issue
I first tried pointing my domain using the load balancer and a cert setup through the certificate manager but that didn’t work so figured it must be something with how the load balancer handles the certificate and went to plan b.
I changed the domain to point directly at the public ip of the ec2 instance and then setup an SSL cert using the bitnami lets encrypt option.
I can get to the parse dashboard using https just fine as long as I have the serverUrl option set to http:// and NOT https://. As soon as I switch to https there it can no longer connect to the api and I get cors errors (No ‘Access-Control-Allow-Origin’ header is present on the requested resource.).
I’m assuming somewhere somehow I need to add Header set Access-Control-Allow-Origin “*”. I tried setting this in the apache/vhosts directory on both the parse-vhost and parse-https-vhost files and restarted apache but no luck. Tried throwing it into the httpd.conf file as well but no luck.
Do I need to somehow set this up in an express middleware somewhere? This doesn’t really look like any express build I’ve ever seen before so not sure where or how to even go about trying that.
Our app needs to be hipaa compliant so once we are ready to push to production obviously ssl all the way through is a must and especially need the wss:// working.