Android App Sync error

[4ctiv]

Mobile app has a persisten sync issue:

Server logs show powersync write-checkpoint2.json GET requests return 401 as a result of the predecessor error PSYNC_S2106 "Auth Required" triggered when "reconnect" is selected in app interface

Client shows:
Syn Error HTTP 301
SyncResponseException: 301 Moved Permanently

Playstore comments suggest I am not the only one having an Issue like this.

Issues that might be related: #131 , #156

---

Setup:

• Docker Server (docker-compose.yaml mit prod.env) (ARM Pi4b, Server v2.7.0a2+git6050749, Powersync v1.25.0)

• changed env: JWT, SITE_URL, SECRET_KEY, ALLOW_REGISTRATION, CELERY_FLOWER_PASSWORD

• changed powersync.yaml storage.uri to PS_DATABASE_URI // defaut would result in powersync fail

• Client: Android 12 (Miui), App v2.0.57

[EtheriousNight]

I have found my issue. I used to use two config-files through my docker-compose.override.yml file. In there was my error with the wrong SITE_URL Environment-Variable... Mabye this is also your Problem? @4ctiv

Old Commend

Hello, I have the same Issue with my setup and wanted to add some more context what not worked for me.

I worked throught these documentation sites:

1. https://wger.readthedocs.io/en/latest/administration/errors.html#wrong-pagination-links
2. https://wger.readthedocs.io/en/latest/administration/errors.html#mobile-app-reports-sync-service-unavailable

Both exactly implemented and checked like with the written confirmation steps.

Two things that may be wierd would be that "https://your.wger.url/ps/" gives me the following response: {"error":{"code":"PSYNC_S2002","status":404,"description":"The path does not exist on this server","details":"The path GET \"/\" does not exist on this server","severity":"info","name":"RouteNotFound"}}, but that could be completely normal.

The second one would be that SITE_URL is configured to "https://your.wger.url" but under "https://your.wger.url/api/v2/powersync-token" the "powersync_url"-field points to "http://your.wger.url/ps/".

Mabye the last one is the problem but i found no setting to set "powersync_url" to use https. If I use the given URL with curl I get the "301 Moved Permanently" message. In my browser it redirects me perfectly to https. The app seems to not handle this properly.

For context my reverse-proxy conf:

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name your.wger.url;
    include /config/nginx/ssl.conf;

    location / {
        proxy_pass http://wger-nginx-1;

        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host $http_host;
        proxy_set_header X-Forwarded-Port 443;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";

        proxy_read_timeout 86400s;
        client_max_body_size 100M;
    }

    location ~ /\.ht {
        deny all;
    }
}

Context from the App:

App: 2.1.0
Server: 2.7.0a2

Error Message from the app:

server: self-hosted
connected: false, connecting: false, downloading: false, uploading: false
last successful sync: never
pending uploads: 0
checkpoint request: target -, seen -, applied -
local buckets: last op -, ops since checkpoint -, oplog rows 0
error (HTTP 301): SyncResponseException: 301 Moved Permanently

[4ctiv]

I have found my issue. I used to use two config-files through my docker-compose.override.yml file. In there was my error with the wrong SITE_URL Environment-Variable... Mabye this is also your Problem? @4ctiv

Old Commend

Hi,
I dont think that is the problem as I have run ripgrep rg 'SITE_URL' in my project and found SITE_URL exactly once.
I run it via docker and realized just now that latest referes to v2.7-alpha instead of latest stable v2.6 so I will switch to that and see if that is the problem.

UPDATE:

The version was not the issue clean install using version 2.6 still has the same error.
Thugh I have the same error:

{
  "error": {
    "code": "PSYNC_S2002",
    "status": 404,
    "description": "The path does not exist on this server",
    "details": "The path GET \"/\" does not exist on this server",
    "severity": "info",
    "name": "RouteNotFound"
  }
}

powersync logs show the following on app connection attempt

[
  {
    "duration_ms": 5,
    "level": "info",
    "message": "GET /write-checkpoint2.json?client_id=c46c976f-8767-40cc-b392-fcb967ca3f0b",
    "method": "GET",
    "path": "/write-checkpoint2.json?client_id=c46c976f-8767-40cc-b392-fcb967ca3f0b",
    "rid": "h/01a062a2-e598-72dc-a312-13c12827c762",
    "route": "/write-checkpoint2.json",
    "status": 401,
    "timestamp": "2026-09-02T15:00:37.917Z"
  },
  {
    "errorData": {
      "code": "PSYNC_S2106",
      "description": "Authentication required",
      "name": "AuthorizationError",
      "status": 401
    },
    "is_service_error": true,
    "level": "error",
    "message": "Request failed [PSYNC_S2106] Authentication required",
    "name": "AuthorizationError",
    "rid": "h/01a062a2-fd84-7503-8553-c856855c20c2",
    "route": "/write-checkpoint2.json",
    "stack": "AuthorizationError: [PSYNC_S2106] Authentication required\n    at authorizeUser (file:///app/packages/service-core/dist/routes/auth.js:24:20)\n    at Object.authUser [as authorize] (file:///app/packages/service-core/dist/routes/auth.js:17:12)\n    at Module.executeEndpoint (file:///app/libs/lib-services/dist/router/endpoint.js:12:59)\n    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n    at async Object.handler (file:///app/packages/service-core/dist/routes/route-register.js:38:50)",
    "timestamp": "2026-09-02T15:00:44.039Z"
  },
  {
    "duration_ms": 6,
    "level": "info",
    "message": "GET /write-checkpoint2.json?client_id=c46c976f-8767-40cc-b392-fcb967ca3f0b",
    "method": "GET",
    "path": "/write-checkpoint2.json?client_id=c46c976f-8767-40cc-b392-fcb967ca3f0b",
    "rid": "h/01a062a2-fd84-7503-8553-c856855c20c2",
    "route": "/write-checkpoint2.json",
    "status": 401,
    "timestamp": "2026-09-02T15:00:44.042Z"
  }
]

What I failed to mention is that I have my service exposed via cloudflare tunnel maybe this is relevant 😅

[EtheriousNight]

Okay, also checked my version and I use the alpha version 2.7.0a2 and it works with that (I get past this 301 Error). The Output from the URL "https://your.wger.url/ps/" seems to be normal as the syncing works with my setup.

To really exclude the from SITE_URL being the issue. Can you confirm that the key "powersync_url" in the output from "https://your.wger.url/api/v2/powersync-token" shows the same value as your SITE_URL with the same Schema (http or https)?

Another thing to check would be if SITE_URL is really set in the web-container from wger. Here is the command: docker compose exec web ./manage.py shell -c "from django.conf import settings; print(repr(settings.SITE_URL))

[4ctiv]

Okay, also checked my version and I use the alpha version 2.7.0a2 and it works with that (I get past this 301 Error). The Output from the URL "https://your.wger.url/ps/" seems to be normal as the syncing works with my setup.

To really exclude the from SITE_URL being the issue. Can you confirm that the key "powersync_url" in the output from "https://your.wger.url/api/v2/powersync-token" shows the same value as your SITE_URL with the same Schema (http or https)?

Another thing to check would be if SITE_URL is really set in the web-container from wger. Here is the command: docker compose exec web ./manage.py shell -c "from django.conf import settings; print(repr(settings.SITE_URL))

• docker compose exec web ./manage.py shell -c "from django.conf import settings; print(repr(settings.SITE_URL))" -> http://wger.[...].de/
• powersync_url -> http://wger.[...].de/ps/

Ah seem like this is the issue it tries to access http ! (That woud explain 301 redirect).
It must have worked as I have set CSRF_TRUSTED_ORIGINS to the correct domain.
Currently restarting the server to check if this is the fix

Thx

[EtheriousNight]

Did it work? I'm curious! xD

[4ctiv]

Yes I have created some data to check if sync works.

Issue was http instead of https in SITE_URL (sorry I missed that)

Thank you very much ! I will close this issue now