View more context

 

MichalKleiner

anyway… we’ve encountered the same issue with Josh and yes, it can be fixed by the proxy config update

gregsmirnov

Hello, we have similar setup, SSL connection to Nginx reverse-proxy and then HTTP connection to Apache server. All projects configured with (SS3) Director.alternate_protocol = 'https' to generate proper links. SS4 simplified configuration and all you need is to set SS_BASE_URL to external url.

gregsmirnov

@MichalKleiner docker nginx-proxy has 2 modes how to forward connection. default is to connect with http.

Josh

Thanks @MichalKleiner, good to see it wasn’t just me having issues. RPAF has done the trick for now, so I’ve incorporated it into the Apache Dockerfile for the meantime.

MichalKleiner

thanks @gregsmirnov… our issue is that we could have several domains and need something universal independent of SS itself

Josh

@MichalKleiner that’s exactly right. In my Dockerfile I’m extending the official httpd image, compiling the mod_rpaf extension, and then loading it via an Apache conf file.

Since this image is mainly used for dev, I added the following under the RPAF_ProxyIPs:

  1. RPAF_ProxyIPs 127.0.0.1 172.16.0.0/16 192.168.0.0/16 10.0.0.0/24
brett.tasker

I think silverstripe looks for HTTP_X_FORWARDED_PROTOCOL rather than HTTP_X_FORWARDED_PROTO. So you may need to define this header in Nginx to match the HTTP_X_FORWARDED_PROTO header.