-
-
Notifications
You must be signed in to change notification settings - Fork 201
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
elabftw behind a firewall/proxy: update - email - timestamp - blockchain #5090
Comments
Hello, I know for a fact that eLabFTW is deployed in very restrictive environments, ,exactly like the one you describe, and works well. What is the value of |
Hello, OK, this sounds very good. What is the point of providing the proxy server information in the admin panel when this is provided in the /etc/elabftw.yml ? Thank you! Best regards from Jena |
What do you mean? The YAML file has no options for egress proxy configuration. It's only that setting in the elabftw/src/Make/MakeBloxberg.php Lines 67 to 68 in b193d9f
I know for rfc3161 timestamps and bloxberg timestamps, it uses this setting, but for smtp you'll need to allow trafic on the smtp port from the vm to your smtp server. For example, one such system has this value for proxy setting in Sysconfig Panel: |
Thank you for the the clarification. We will test it with the proxy admin. |
Detailed description of the problem
We are running elabftw now behind a firewall. Access to the outside world is only possible through a proxy server.
Updating the docker images with elabctl was successful by telling docker the proxy configuration via the systemd method (read carfully https://docs.docker.com/config/daemon/systemd/)
However email - timestamp and blockchain is still not possible, despite giving the proxy server information to the sysadmin panel > server > Address of the proxy
Expected Behavior
access possible
Steps to reproduce the behavior
outside the firewall everything worked great
Do you have any idea what may have caused this?
proxy setting not known to these functions
Do you have an idea how to solve the issue?
give the functions access to proxy information
What is your docker-compose configuration?
Output of
uname -a
Output of
cat /etc/os-release
Output of
docker info
Relevant php error log entry
Additional information
Thank you for your great work.
The text was updated successfully, but these errors were encountered: