mobile access is not working

[woreibi]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

when activating mobile api under authentication and also under profile by setting a password then using mobile app "Readrops" , I am getting HTTP 404 on mobile app. the nginx log shows http OK but mobile app never completes sign in process.

I used docker image from freshrss team and it appears to work there on mobile app. It seems image from linuxserver for freshrss has an issue with mobile app authentication.

I am using linuxserver / freshrss image with a https and cert so I am accessing it via https and FQDN name. Same test was conduct with image from freshrss team and issue only exist with mobile app when using linuxserver/freshrss image.

Would you be able to verify that feature works or not

thank you,

Expected Behavior

Mobile app readrops should be able to sign in and authenticate successfully using mobile app authentication builtin freshrss.

Steps To Reproduce

activate mobile api under authentication set password for mobile api use https:///api/greader.php in readrops mobile app with admin account and password that was set in mobile api under profile.

Environment

docker compose

CPU architecture

x86-64

Docker creation

version: "2.1"
services:
  freshrss:
    image: lscr.io/linuxserver/freshrss:latest
    container_name: freshrss
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - /path/to/data:/config
    ports:
      - 80:80
    restart: unless-stopped

Container logs

nginx logs shows when mobile api is trying to access freshrss:

[13/Jan/2023:09:04:01 -0800] "POST /api/greader.php/api/gread                                                                                                    er.php/accounts/ClientLogin HTTP/2.0" 400 12 "-" "okhttp/4.9.1"

[github-actions[bot]]

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue is locked due to inactivity