MichalKleiner

You can also set your base URL for dev config

  1. ---
  2. Only:
  3. Environment: 'dev'
  4. ---
  5. SilverStripe\Control\Director:
  6. alternate_base_url: https://www.project.loc
MichalKleiner

adding trusted proxy settings in the env file

  1. SS_TRUSTED_PROXY_IPS="127.0.0.1,192.168.0.0/16,172.16.0.0/12,10.0.0.0/8"
  2. SS_TRUSTED_PROXY_PROTOCOL_HEADER="HTTP_X_FORWARDED_PROTO"
  3. SS_TRUSTED_PROXY_HOST_HEADER="HTTP_X_FORWARDED_HOST"
  4. SS_TRUSTED_PROXY_IP_HEADER="HTTP_X_FORWARDED_FOR"
clodeindustrie

How do you get your SS install to act like it's on HTTPS? the page loads right but it tries to load my assets through http

MichalKleiner

we use paulczar/omgwtfssl in docker-compose to generate SSL certs that the proxy can use

clodeindustrie

I guess I will have to share the certs with the SS install and forward all the right headers

clodeindustrie

right, I had my proxy all set up with Let'sEncrypt I had hoped I could get away with not running my backend (the SS app) on https too.

brett.tasker

https://github.com/jwilder/nginx-proxy There README is actually pretty good and tells you how to configure SSL and also how to set Proxy Headers if needed (e.g. Forwarded Proto, Real IP, etc).

You will probably need to set it up to set the correct Proxy Headers for your SilverStripe installation. And then add your SSL KEY / CRT as per the docs on the README

Show 1 attachment(s)
GitHub  
jwilder/nginx-proxy

Automated nginx proxy for Docker containers using docker-gen - jwilder/nginx-proxy

Hide attachment content
clodeindustrie

hey, anyone running SS on Docker behind jwilder/nginx-proxy? Just wondering about setting it up to run properly on HTTPS

r3v3rb

Hmm, windows just updated and now my vagrant boxes cannot access the internet - anyone else had this issue?

brett.tasker

What provider are you using?

It is probably an issue with your Provider (rather than Vagrant) and it may also need updating to the latest version.

r3v3rb

Yep, re-installation of Virtualbox and removal of all previously installed virtual network cards fixed the issue after the windows update.

👍 (1)