Homestead SSL

SSL is default. You shouldn't have to do anything. Does https://localhost: 44300 work?

@svpernova09 thx, https://localhost:44300 is working, but when i specify https://homestead.app it will show "This site can’t provide a secure connection" in chrome

I would have to see your Homestead.yaml, and full vagrant up output be much more help.

@svpernova09 kindly view the following files

Homestead.yaml https://www.dropbox.com/s/dko9foi51ohofgm/Homestead.yaml?dl=0

Vagrant.log https://www.dropbox.com/s/59tbdnv2kvrwsa5/vagrant.log?dl=0

@terry_low

Map each site as it's own folder in your folder's mapping.

folders:
    - map: F:/Php/Laravel/homestead.app
      to: /home/vagrant/homestead.app
    - map: F:/Php/Laravel/runner.app
      to: /home/vagrant/runner.app

sites:
    - map: homestead.app
      to: /home/vagrant/homestead.app/public
    - map: runner.app
      to: /home/vagrant/runner.app/public     

it still doesnt works, btw i found that, once i change my hosts file and point to 127.0.0.1 homestead.app and ssl will works, but will not works with 192.168.10.10 homestead.app

Anybody had any joy with this?

If you're having issues with this, open an issue on github: https://github.com/laravel/homestead/issues/new

You would still need to get your local OS to trust the certificates generate by Homestead.

This article shows how to do it on macOS. https://medium.com/@adnanxteam/how-to-setup-https-with-laravel-homestead-ad7915470fa8

Not sure the steps for Windows 10 though.

@alexagui I don't think that will help. Google owns the .app TLD, and a few months ago they started forcing Chrome to use https on all .app domans.

In addition to the expected demand, Google is requiring HTTPS for all. app websites. This built-in security protects against ad malware, tracking injection by internet service providers, and safeguards against spying on open Wi-Fi networks, the company explains.

https://techcrunch.com/2018/05/01/google-is-launching-app-domains-the-first-tlds-secured-with-built-in-https/

Use .test for your TLD's.

@Cronix Good point about just using test.

dev, app and local aren't worth the hassle, especially if you're using Chrome.

I published a blog post on how to setup SSL for your local environment. There's a short screencast for Chrome. And detailed steps for the 3 major browsers.

https://www.eaglepeakweb.com/blog/how-to-enable-ssl-https-tls-laravel-homestead