Parse-vhost.conf file does not exist when trying to Force HTTPS For Parse Server Requests

tiago7futre 2020-12-10 08:42:02 UTC #1

Keywords: Parse - Virtual Machines - Technical issue - Secure Connections (SSL/HTTPS)
Description:
https://docs.bitnami.com/bch/apps/parse/administration/forcehttps/

I am trying to force https for Parse server requests using the link above.

I am able to access apache2 using this directory /stack/apache2/conf

but not /opt/bitnami/apache/conf/

is there a way to solve this issue?

jota 2020-12-10 10:28:12 UTC #2

Hi @tiago7futre,

We have a Support Tool that will gather relevant information for us to analyze your configuration and logs. Could you please execute it on the machine where the stack is running by following the steps described in the guide below?

How to Run the Bitnami Support Tool in a cloud image or virtual machine

Please note that you need to paste the code ID that is shown at the end.

tiago7futre 2020-12-10 10:42:20 UTC #3

Thank you this is the ID:
71487d0d-528b-a8fa-ae75-78129abc8327

tiago7futre 2020-12-11 08:21:26 UTC #4

I am also having the exact same issue as this post. When I try access the parse dashboard using https I am unable to do so only using http. When I try using https it also says that I have an invalid certificate. (https://xx.xxx.xx.xx)

I have an e2 instance for the parse server but when I try access the Public IPv4 DNS (www.ec2-xx-xxx-xx-xx.us-west-2.compute.amazonaws.com) it says server IP address could not be found.

jota 2020-12-11 11:01:44 UTC #5

Hi @tiago7futre,

You are using an old version of the Bitnami Parse solution and that's why you can't find the "parse-https-vhost" file. In you case, you need to add the configuration to the /opt/bitnami/apache2/conf/bitnami/bitnami.conf file. However, I just saw that you ran the Bitnami HTTPS configuration tool and it configured the SSL certificate and the redirections to https. I accessed your site and it's working properly for me.

$ curl -LI rootconnection.co
HTTP/1.1 301 Moved Permanently
Date: Fri, 11 Dec 2020 10:59:29 GMT
Server: Apache
Location: https://rootconnection.co/
Content-Type: text/html; charset=iso-8859-1

HTTP/2 200
date: Fri, 11 Dec 2020 10:59:29 GMT
server: Apache
last-modified: Mon, 07 Dec 2020 09:38:57 GMT
etag: "fa27e0-290-5b5dc986183c2"
accept-ranges: bytes
content-length: 656
vary: Accept-Encoding,User-Agent
content-type: text/html

Is there anything more you need help with?

Thanks

tiago7futre 2020-12-11 11:40:20 UTC #6

Thank You.

I am now struggling with accessing my parse dashboard using https and can only access it using the Public IPv4 address with http and cannot access using the Public IPv4 DNS anymore through aws ec2 instance.

Any help with this would be much appreciated.

jota 2020-12-14 11:25:43 UTC #7

A post was merged into an existing topic: Bncert-tool Domain resolves to a different IP when configuring https

tiago7futre 2020-12-14 11:25:13 UTC #8

This is the issue I have at the moment.

system 2020-12-28 11:25:43 UTC #9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!