No answer from api

[akym-pavliuk]

The problem

I srarted docker container on Linux. In one moment a few different users have no answer from api. Not working "GET v1/groups", "v2/send". Received answer "error: process killed as timeout reached"
But container is up and "v1/about" is working
Reinstall latest version, reboot laptop - same problem

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?

Native Mode

What's the architecture of your host system?

x86-64

Additional information

No response

[Cempakers87]

I have the same issue, not working "GET v1/groups" and "v2/send" attachment.

[akym-pavliuk]

UPD: switched to MODE=normal and it worked

[Cempakers87]

UPD: switched to MODE=normal and it worked

ah ok i will try it and report back here

[Cempakers87]

thanks @akym-pavliuk worked for me

but im still curious why native mode not working

[MStrecke]

I've had the same problem and the work-around seems to work here as well... for the moment.

[jneidel]

I have the same problem in native mode, despite being on an older version (0.91).

Despite not being able to receive my messages because of process killed as timeout reached, the messages are marked as read for the sender.

Can confirm reverting to normal mode as a temporary solution.

[0fflineuser]

Hi,
I am having the same problem and the work-around also works.

[kkro]

Same problem here after running for a long time without any problem.

[bbernhard]

That's strange. Usually the native mode should perform better than the normal mode. In case you are running in a timeout, it might make sense to increase the timeout when doing a receive with the timeout query parameter. See: https://bbernhard.github.io/signal-cli-rest-api/#/Messages/get_v1_receive__number_

[walter-in-space]

Same problem here, fixed with normal mode. May there a change at signal?

[bbernhard]

Same problem here, fixed with normal mode. May there a change at signal?

The native mode should be the same as the normal mode, except that it is compiled to native code and therefore doesn't use the Java VM. So it should behave the same as the normal mode.

[Flamekebab]

I'm also affected by this. Switched out native for normal and functionality was restored.

[tech1ndex]

+1 and switching to normal also worked for me.

[bbernhard]

Did you experience the issue after upgrading to the latest version or did the issue appear at random?

[akym-pavliuk]

Did you experience the issue after upgrading to the latest version or did the issue appear at random?

Just random, during regular work