Matthias

(3, Kaffeetwete, Mitte, Brunswick, Lower Saxony, 38100, Germany)

Matthias
2 weeks ago from [ˈloma] | Friendica — (3, Kaffeetwete, Mitte, Brunswick, Lower Saxony, 38100, Germany) •

!Friendica Support
With the switch to the RC branch of Friendica, a user with Android 10 and 11 are have problems logging in with a mobile app (Fedilab, Raccoon, Relatica).

I can log in without any problems from my devices (2 Android; 1 iPhone).

I cannot find any error messages relating to OAuth, credentials or other terms in the logs.

Does anyone know what the problem is? What should I look for in the logs to find a message that provides information about the problem?

!Friendica Support

Have a look at the access-logs of your webserver. Hopefully, these three apps send user agent strings with their name. Then have a look if the request returns some 4** or 5** error or some 2**. If you find some 4**, please tell here with the log.

Matthias

2 weeks ago from [ˈloma] | Friendica •

@Michael 🇺🇦 These are hits from the same IP address.
Furthermore, there are no issues with registrations.

xxx - - [30/Sep/2025:07:51:26 +0200] "GET /.well-known/host-meta HTTP/2.0" 200 487 "-" "SubwayTooter/5.549 Android/11"
xxx - - [30/Sep/2025:08:37:44 +0200] "POST /api/v1/push/subscription HTTP/2.0" 401 175 "-" "Tusky/31.1 Android/11 OkHttp/5.1.0"
xxx - - [30/Sep/2025:08:37:44 +0200] "GET /api/v1/push/subscription HTTP/2.0" 401 175 "-" "Tusky/31.1 Android/11 OkHttp/5.1.0"
xxx - - [30/Sep/2025:08:37:44 +0200] "DELETE /api/v1/push/subscription HTTP/2.0" 401 175 "-" "Tusky/31.1 Android/11 OkHttp/5.1.0"

@Michael 🇺🇦

@container01@loma.ml

2 weeks ago •

@Matthias
I am the 'suspicious' user and can no longer use any Android App.
(Fedilab, Moshidon, Raccoon, Subway Tooter, Tusky)
Getting from App's only error messages like:
Fedilab: 'Die App konnte kein Token abgerufen'
Raccoon: 'Invalid Credentials'
Moshidon: 'Error parsing an API error'
Tusky (all possible variations) 'Kontoinformationen konnten nicht abgerufen werden'
Subway Tooter: '(missing response body) (HTTP 500) loma.ml GET https://loma.ml/API/V1/accounts/verify_credentials'

All in 'https://loma.ml/settings/oauth' already cleared, without effect.

@Matthias

Michael 🇺🇦

2 weeks ago •

The HTTP error 500 should be findable in the logs. It indicates some server side error.

Matthias

2 weeks ago from [ˈloma] | Friendica •

@Michael 🇺🇦 @@container01@loma.ml
The requests all come from the same IP address as above:

xxx - - [30/Sep/2025:08:17:41 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "SubwayTooter/5.549 Android/11"
xxx - - [30/Sep/2025:08:20:09 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "MoshidonAndroid/2.3.0+fork.110.moshinda-github"
xxx - - [30/Sep/2025:08:22:30 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "MoshidonAndroid/2.3.0+fork.110.moshinda-nightly+@2025-06-15"
xxx - - [30/Sep/2025:08:25:00 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "MoshidonAndroid/2.3.0+fork.110.moshinda-nightly+@2025-06-15"
xxx - - [30/Sep/2025:08:31:57 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "Mastify/1.4.24-alpha And

@Michael 🇺🇦 @@container01@loma.ml
The requests all come from the same IP address as above:

xxx - - [30/Sep/2025:08:17:41 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "SubwayTooter/5.549 Android/11"
xxx - - [30/Sep/2025:08:20:09 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "MoshidonAndroid/2.3.0+fork.110.moshinda-github"
xxx - - [30/Sep/2025:08:22:30 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "MoshidonAndroid/2.3.0+fork.110.moshinda-nightly+@2025-06-15"
xxx - - [30/Sep/2025:08:25:00 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "MoshidonAndroid/2.3.0+fork.110.moshinda-nightly+@2025-06-15"
xxx - - [30/Sep/2025:08:31:57 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "Mastify/1.4.24-alpha Android/11 OkHttp/4.12.0"
xxx - - [30/Sep/2025:08:32:44 +0200] "GET /api/v1/accounts/verify_credentials? HTTP/1.1" 500 - "-" "Kaiteki/1.0"
xxx - - [30/Sep/2025:08:35:12 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "okhttp/4.12.0"
xxx - - [30/Sep/2025:08:35:23 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "okhttp/4.12.0"
xxx - - [30/Sep/2025:08:38:16 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "Tusky/31.1 Android/11 OkHttp/5.1.0"
xxx - - [30/Sep/2025:08:39:18 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "SubwayTooter/5.549-noFcm Android/11"
xxx - - [30/Sep/2025:09:01:23 +0200] "GET /api/v1/accounts/verify_credentials HTTP/2.0" 500 - "-" "MegalodonAndroid/2.1.6+fork.110"

@Michael 🇺🇦 @@container01@loma.ml

Michael 🇺🇦

2 weeks ago •

Enable the debug level. Then the user should try again. Then grep for the same pattern in the friendica log. You should find the line GET /api/v1/accounts/verify_credentials. In that line you will find the parameter request-id followed by some string. Please then grep all lines with that string.

Matthias

2 weeks ago from [ˈloma] | Friendica •

@Michael 🇺🇦
We have now tried 5 different Android devices + 2 iPhones with different accounts. All logins were successful. We also had to try a Sony with Android 7 again ;) No problem here either with Tusky.

@@container01@loma.ml

@Michael 🇺🇦 @@container01@loma.ml