# Planning for OpenEMR 5.0.2 release **URL:** \ **Category:** OpenEMR Development\ **Created:** [March 29, 2019, 7:26am UTC](https://community.open-emr.org/t/planning-for-openemr-5-0-2-release/11858 "2019-03-29T07:26:25Z")\ **Posts on this page:** 1\ **Showing post:** 72
**Author:** ![Ralf\_Lukner](https://community.open-emr.org/user_avatar/community.open-emr.org/ralf_lukner/32/11962_2.png) [@Ralf\_Lukner](https://community.open-emr.org/u/Ralf_Lukner)\ **Post date:** [August 5, 2019, 2:26am UTC](https://community.open-emr.org/t/planning-for-openemr-5-0-2-release/11858/72 "2019-08-05T02:26:59Z")
I started over, making sure that I have the consistent VPC and subnets, and that seems to have launched me past that database connectivity problem for now. The ssl configuration of the replicated EC2 image is redirecting to the secure connection … in other words it won’t allow a http connection to the replicated image and immediately redirects to my domain with a https:// and I cannot remember how to “undo” this behavior. I know there must be a .cnf or .conf file somewhere that controls the redirection of http to https (forcing a https connection). Update — I eliminated a .htaccess file and modified all the relevant .conf and .cnf files I could find. Finally sent a message to Amazon Tech Support to help me out on this. –Ralf --- _[View the full topic](https://community.open-emr.org/t/planning-for-openemr-5-0-2-release/11858)._