-
Notifications
You must be signed in to change notification settings - Fork 40
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
ProxyPass with https SNI on apache and http transport locally #40
Comments
I've just found in the
This should definitely be configurable by an environment variable which states that the requests can be proxied before with the encryption end point. |
I ran into the same problem trying to run it with a nginx reverse proxy. |
By default, metasfresh-docker runs non-SSL since it's easier for testing and currently we don't have a function inside the containers to use eg. Let's Encrypt for generating SSL keys/certs. If you're deploying metasfresh on a direct-accessible system, you can follow these Guidelines: Setting "https://myserver.com" in the appropriate line in your However running metasfresh on a reverse proxy, you will also have to setup your nginx/apache conf on your reverse-proxy similar to this file: https://github.com/metasfresh/metasfresh-docker/blob/master/webui/sources/configs/metasfresh_webui_ssl.conf ... replacing the server-names (eg.: webapi) with the server you're running the docker-stack on of course and adding a new reverse-proxy entry to point to the webui-location / -port instead of using |
Hi @metas-jb I have tried the adaptation of the configuration for my reverse proxy. In the docker compose file I set WEBAPI_URL=https://myurl but the REST API is still addressed via http. What can I do? |
Is this a bug or feature request?
Kind of both, but first of all a bug
What is the current behavior?
The app does insecure reloads. The served
config.js
has the following content:Which are the steps to reproduce?
80:80
and443:443
to127.0.0.1:8080:80
and127.0.0.1:8443:443
What is the expected or desired behavior?
in the
config.js
the URLs should behttps
URLsThe text was updated successfully, but these errors were encountered: