0

I got a Laravel App running on an Apache server. I've configured VirtualHost to locally access the app with URL:

https://www.infoalquiler.com.ar/

Despite the app is working properly, I'm getting a "Not secure" message in the browser, like this:

Browser

I've tried to generate a certificate with OpenSSL, like this:

leandro@Leandro:~/Proyectos/infoalquiler$ sudo openssl req -x509 -nodes -days 365  -newkey rsa:2048  -keyout /etc/apache2/ssl/apache.key  -out /etc/apache2/ssl/apache.crt
....+.+..................+..+++++++++++++++++++++++++++++++++++++++*.......+...+++++++++++++++++++++++++++++++++++++++*......+........+....+......+.........+........+......+.........++++++
..+.......+.....+++++++++++++++++++++++++++++++++++++++*....+.+......+...+..+.+..+...............+.......+...+..+.+++++++++++++++++++++++++++++++++++++++*.....+...+............+..................+......+...+.+.................+....+...+.....+...............+...............+.......+........+......+..........+.....+....+......+......+...+..+....+.....+....+.....+.+..+...+....+.................+...+...+...+.+......+..............+.........+....+...............+..+.........+.+...+.....++++++
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:AR
State or Province Name (full name) [Some-State]:BA
Locality Name (eg, city) []:CABA
Organization Name (eg, company) [Internet Widgits Pty Ltd]:
Organizational Unit Name (eg, section) []:
Common Name (e.g. server FQDN or YOUR name) []:Leandro Caplan
Email Address []:[email protected]

Then,I've tried to import the certificate to Chrome like this:

Import

So then, I got a window asking for a password like this:

Pass

The page is still showing the "Not secure" warning.

Any suggestion for solving this?

Thanks and best regards!

Leandro

2
  • 'The page is still showing the "Not secure" warning.' - so? Let it then, what is the problem with that? You are obviously able to access the site using an HTTPS connection - only the browser isn't able to verify your self-created certificate against any known signing authority. But that should not stop you from testing and developing locally, does it? Commented yesterday
  • In my experience, creating a self-signed certificate which browsers would accept as truly secure is too much effort for the benefit. Me, personally (and all developers I know) just live with that message when developing locally. Commented yesterday

0

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.