-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker with Proxy - OK - but SSL? #396
Comments
I did not try it with docker but to use Typemill with a proxy, you have to activate the X-Forwarded-Headers in the developer section of the system settings. Did you try that already? |
Yes, of course I did first... 😁
trendschau ***@***.***> schrieb am Do., 13. Apr. 2023, 19:12:
… I did not try it with docker but to use Typemill with a proxy, you have to
activate the X-Forwarded-Headers in the developer section of the system
settings. Did you try that already?
—
Reply to this email directly, view it on GitHub
<#396 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK35VR4ID3MMMO5MSXT4ZMLXBAXWBANCNFSM6AAAAAAW5KEJBM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
You can try if it works now with Typemill Version 2.1.1. Not super sure about your setup, the Docker image does not support SSL, not sure if you have docker behind a ssl-proxy? Never tried that, not sure if it works. |
I tested it with version 2.3.0. It should work, but there are many different configurations depending on your environment. In version 2.3.0 you can force an base-url with something like "https://myproxyurl.io" and that should work (it worked for me and for a client). Let me know if this helps. |
I try to use typemill with a reverse proxy with SSL. It works good with http. It works so far with HTTPS, as the source of the side is delivered, but not the assessments. I recognized, that there is a rewrite-rule to several paths to index.php.
Maybe this is a barrier for the reverse proxy ? Or is there somewhere a setting I have to adjust?
The text was updated successfully, but these errors were encountered: