Bernhard B.
Bernhard B.
> I started the container with the following command: $ sudo docker run -d --name signal-api --restart=always -p 8080:8080 -v $HOME/.local/share/signal-api:/home/.local/share/signal-cli -e 'MODE=json-rpc' bbernhard/signal-cli-rest-api > > Under /v1/about I get...
> I also tried the hints from issue #231, but with no success. I am on a network with no proxy or so (although it is quite slow, LTE) and...
Please give that version a try: `bbernhard/signal-cli-rest-api:0.158-dev`. This image uses the latest released `signal-cli` version. Does that change anything? You mentioned, that you are using the `normal` mode. Do you...
> We are calling the receive endpoint from hour to hour. okay, that should be fine. > WARN ManagerImpl - No profile name set. When sending a message it's recommended...
Here you go: `bbernhard/signal-cli-rest-api:0.160-dev`
Here you go: `bbernhard/signal-cli-rest-api:0.181-dev`
Can't reproduce that issue. Have you maybe set the `SIGNAL_CLI_CONFIG_DIR` environment variable before (to some other value)?
If you are using the normal/native mode, there is the ìgnore_attachments` parameter (https://bbernhard.github.io/signal-cli-rest-api/#/Messages/get_v1_receive__number_)
> I have a similar issue as OP - large attachments folder, which I don't really need or want. > > If I understood the comments correctly, if I was...
`process killed as timeout reached` indicates that the receive endpoint is taking longer than the 10sec timeout you've specified for receiving data. Please try to increase the `timeout` URL parameter...