ios-app
ios-app copied to clipboard
iOS/ipadOS log in error : "Unknown error"
Hello, I'm new to Wallabag. I have installed the server as a docker container using the following docker compose:
version: '3'
services:
wallabag:
image: wallabag/wallabag:2.5.4
container_name: wallabag
environment:
- MYSQL_ROOT_PASSWORD=wallaroot
- SYMFONY__ENV__DATABASE_DRIVER=pdo_mysql
- SYMFONY__ENV__DATABASE_HOST=db
- SYMFONY__ENV__DATABASE_PORT=3306
- SYMFONY__ENV__DATABASE_NAME=wallabag
- SYMFONY__ENV__DATABASE_USER=wallabag
- SYMFONY__ENV__DATABASE_PASSWORD=wallapass
- SYMFONY__ENV__DATABASE_CHARSET=utf8mb4
- SYMFONY__ENV__MAILER_HOST=
- SYMFONY__ENV__MAILER_USER=~
- SYMFONY__ENV__MAILER_PASSWORD=~
- [email protected]
- SYMFONY__ENV__DOMAIN_NAME=http://myserver.lan.mynetwork.local:8200
- SYMFONY__ENV__SERVER_NAME="Your wallabag instance"
ports:
- "8200:80"
volumes:
- /wallabag/images:/var/www/wallabag/web/assets/images
healthcheck:
test: ["CMD", "wget" ,"--no-verbose", "--tries=1", "--spider", "http://localhost"]
interval: 1m
timeout: 3s
depends_on:
- db
- redis
db:
image: mariadb:10.8.2
container_name: wallabag-db
environment:
- MYSQL_ROOT_PASSWORD=wallaroot
volumes:
- /wallabag/data:/var/lib/mysql
healthcheck:
test: ["CMD", "mysqladmin" ,"ping", "-h", "localhost"]
interval: 20s
timeout: 3s
redis:
image: redis:7.0.11-alpine3.17
container_name: wallabag-redis
healthcheck:
test: ["CMD", "redis-cli", "ping"]
interval: 20s
timeout: 3s
My server runs on port 8200
I installed the wallabagger plugin on firefox and all runs perfectly. I have installed the app wallabag v2 on iOS and ipadOS (wallabag v2 6.2, 9 months old) and both fail with "Unknown error". Nothing in the docker console. These 2 devices are on the same subnet and can access the admin portal through the web GUI.
Can it be the app being too old and not compliant anymore with the latest server's version or the custom port not managed by the app ? Can you please help ?
I'll transfert the issue to the iOS repo, because it seems that everything is working properly on the server side.
hello, could you give me the URL of your instance? if you want to keep it private. just give me the pattern of your url that you put in the application.
Hi @bourvill, The URL looks like this http://myserver.lan.mynetwork.local:8200 I have updated the docker-compose.yml accordingly.
The unknown error is often a sign that the application cannot connect to the server.
Can you also check that the client_id and secret_id identifiers are correct?
I thought it might come from the custom port. So I tried with another docker host on port 80, on the same domain/subnet
- SYMFONY__ENV__DOMAIN_NAME=http://myserver2.lan.mynetwork.local
...
ports:
- "80:80"
and it failed again. I had to put "80:80" instead of just simply "80" otherwise it always redirect to https
Can it be an issue?
ids are correct, directly copied from the browser
I had a look at https://github.com/wallabag/ios-app/issues/2 and tried: http://local_ip:8200 And it worked.
This is unfortunate I have to put the IP in the IOS client, since the web browser on IOS is able to resolve the FQDN BTW, I kept the FQDN in the SYMFONY__ENV__DOMAIN_NAME variable.
Also bookmarking from my browser to the Wallabag app on IOS works, but then if I try to go to that bookmark from the Wallabag app, it cannot resolve.
Does the IOS wallabag app use the system's DNS servers (delivered by local DHCP) or public ones which can be hard coded somewhere ?
Can it be in Shortcuts/AddEntryIntentHandler.swift, function resolveUrl ?
I too have encounered this problem.
using http://local_domain:8081 gives unknown error using http://ip_address:8081 works
iOS browser is able to access (and log in) to http://local_domain:8081
I've also encountered this problem. I've tried all of these methods, none of which have worked:
- http://wallabag.box (DNS record in my Pi-Hole)
- http://wallabag.mywebsite.com (public DNS record for a domain I own)
- http://tailscale-ip:45000 (Tailscale IP address for my server + port number)
I'm away from home, so I can't try a local IP, but 2 & 3 imply it's not a DNS issue.
I'm having the same issue. Have Wallabag installed on vps via YunoHost. I've tried creating new users, deleting API keys and creating new ones, etc. and nothing resolves it.