Too many follow-up request : 21

Hi !

When I want to connect Mattermost Mobile, I receve this message : Too many follow-up request : 21

What is wrong and what I should modify ? Before, it was good but know it doesn’t work any more.

I precise that I have installed with Yunohost.org.

Thank you for your answer.

Thomas

Android App 2.15.0.

No body have a little response ?

I have the same problem.
Clearing Data and reinstalling the app didn’t work.
The server did work initially on mobile.

Edit:
I just read that the new Version 2.16.0 requires server version 9.5.0+.
What should be no problem for us, as our server is on version 9.8.0

Hiya all,
I had to change my iPhone and iPad for newer ones. I backed up my old ones and then restored all apps incl. mattermost clients.
When I tried to enter my mattermost server I got “too many redirects” error.See image.


I have a yunohost server too …

None of the workarounds shown in github or mattermost or yunohost do NOT work … Other iOS devices which were not restored work perfectly well with same version of iOS…
Has any Mattermost developer got any suggestions? It seems to be a nginx redirect issue: log say that it happens when MM is in a subfolder of the server like https://myserver.ynh/mattermost
and it enters a loop redirecting to …/mattermost/mattermost/mattermost/…

I have the same problem here.
It works very well with the URL in the browser and in the desktop-app.
But the Android-App (2.18.1, build 53603 and build 6000536) show this error with the same URL.
Mattermost from docker:
Mattermost Version: 9.10.0
Database Schema Version: 121
Build Number: 9713988960
Database: postgres

The web-server is apache.

The error occurs on two different Andoid OS, one Lineage 21 (latest version) and the other is an two year non updated Android.

Any help is very much appreciated!

Maybe ask in Mattermost

The answer is:
Use an old mattermost client. The newest which is still working is:

Then you can connect and after that you can also upgrade to the newest mattermost client.
I hope that the devs fix this bug. Seems to be related to a path at the end of the domain, so for example: https:mattermost.example.com/mattermost

What is the SiteURL in config.json? If it has a trailing slash, try removing it.

The developers are aware of this issue and are working on a fix.