search

standardnotes / forum

Support from other community members. For 1-on-1 help, please contact help@standardnotes.com.
https://forum.standardnotes.org
200 stars 8 forks source link

Unable to login to local sync server from F-Droid app on graphene-os #3209

Open IAteYourBacon opened 1 year ago

IAteYourBacon commented 1 year ago

I installed the docker server (latest version from today) on a debian 12 server. I have the appimage (v3.167.22) running on my pop_os laptop, it can login and sync with no issues with my local server.

The app I got from F-Droid (v3.167.19) is unable to connect to my local server with the same login credentials.

When I login from the laptop, I see it on the server in auth.log. When I log in from the phone (Graphene-OS), I get nothing on server side and I get a "Failed to fetch" message in red under the password field.

I tried with custom sync server set at http://hostname:3000/ and http://192.168.0.210:3000/, it makes no difference. I checked I can ping the server from the phone. The phone is able to access other services on my LAN no problem. The app has network permissions. If I uncheck the custom sync server and try to login or create an account, I get the same error message.

It looks like the app is unable to open any network connection. Are you aware of a problem with the f-droid version or with graphene-os?

Thank you

IAteYourBacon commented 1 year ago

Is there a HTTPS requirement? can a self signed cert be used? I'm using only LAN access here, 192.168.0.0/24

Also, I tried the aurora store version (v3.167.22) and got the same problem.

effieeee commented 1 year ago

Hi @IAteYourBacon, so far the team has only been able to confirm that the iOS app is able to access local hosted servers in particular, though for the Android app, I'm afraid it still hasn't been fully verified, and I usually advise self hosters to secure their traffic as well.

You may try a self signed certificate in case it might help, though please also double check if your ports are correctly mapped, as shown in our sample docker compose file.

IAteYourBacon commented 1 year ago

Self signed certs don't work. For me, the point of self-hosting is to keep my server private, i.e not accessible from the Internet. So the guide to use Nginx and Let's encrypt didn't work, because Let's encrypt requires public access to the server to create/renew the certificates every 90 days.

For anybody having the same issue, here is what I did I created a new host on a public domain name and webserver I already owned Configured that webserver to use HTTPS with Let's encrypt to serve a blank page Then created a the same FQDN host on my LAN DNS pointing to my server's LAN IP Copied the certs from the public webserver to a local Nginx Configure that local Nginx to proxy to standardnotes:3000 with SSL Have a crontab running ever 6h to pull new certs from public webserver to the local one

This is overly complicated but it works I wonder why the standardnotes android app is unable to use http to connect to a LAN server It does work in the Linux app, is it an android thing? That would save a lot of grief!

nhooram commented 1 year ago

I have the same issue. I'd like to know if there's plans to address this.

RamonAbudAlcala commented 1 month ago

I was having this issue on the Linux desktop, the iOS, Android app, and the self hosted web-app (accessed on Firefox). Using a custom Certificate Authority (only used for my internal services). Error showed at login as the "Failed to fetch" Android and Linux or "Load Failed" on iOS.

I was able to resolve the issue on Linux and iOS and Firefox by loading the certificate authority to the local trust. I did that on Android too, but it seems that the android app is not trusting the user custom Certificate Authorities.

I am not able to use a service like Let's Encrypt as I am not using an official TLD for my internal services.

The android app should support trusting the local Certificate Authorities from the OS, including user-defined ones. BTW, I used the Latest Github apk (via obtanium) and the Play Store version. Both have this problem.

sambal0 commented 1 day ago

Solved: Was not aware that the Web App has to be self hosted. Installed it and now its working with the mentioned certs.

Apps are fine, browser access is not. My self hosted server is working on the iOS and macOS app. When trying to login or create an account through the browser "app.standardnotes.com" it always fails (Chrome/Opera: "Failed to fetch", Safari: "Load failed", Firefox "NetworkError when attempting to fetch resource."). I am using the self hosted server on Docker with a Cloudfare tunnel and their SSL certificates. Additionally, tried it as mentioned above through NGINX with a Let's Encrypt certificate (DuckDNS) but still not working. Any help or updated information on the self signed certs issue?