Closed
Description
The problem
To get the signal-cli to work behind a proxy you can using the JAVA_OPTS environment variable to configure them like so:
JAVA_OPTS=-Dhttp.proxyHost=proxy.server -Dhttp.proxyPort=3128 -Dhttps.proxyHost=proxy.server -Dhttps.proxyPort=3128
However, this fails in json-rpc mode. (It also fails in native mode but I don't know how to fix that.)
It happens because in java-rpc mode signal-cli is run under supervisor as a service, which clears the environment.
The fix is to copy the variable through. Will post patch shortly.
Are you using the latest released version?
- Yes
Have you read the troubleshooting page?
- Yes
What type of installation are you running?
signal-cli-rest-api Docker Container
In which mode are you using the docker container?
JSON-RPC Mode
What's the architecture of your host system?
x86-64
Additional information
No response
Metadata
Metadata
Assignees
Labels
No labels