Can you please suggest the required changes in the Online Deployment
env files in order to use my own NGINX daemon?
I already have NGINX and LetsEncrypt in place, I can forward traffic, but I don’t know what ports are exposed by the Corteza container, aka on what port should I fwd the traffic from NGINX to Corteza.
Hello, the corteza container is running on 80, so you should proxy everything corteza related to that container.
I did exactly that, but it seems that when doing the initial user activation the link is enforcing
https. Because of that the browser is refusing to access the page (mixed http+https).
- accessing the instance via https
- creating the user as expected
- when clicking the “activation link” I’m redirected to a
https link that tries to access a
http URL with the token
At this point I’m stuck, as I have no idea how to enforce
https on Corteza’s URLs.
Can you check the
This should take care of the
https redirect issue, since by default we are checking the
LETSENCRYPT_HOST setting, that you are probably not using.
This should be defined in
I’m not using anything related with
nginx-letsencrypt containers, both run as standalone daemons on the host.