Network error for logining in trilium server in trilium-sender

Question

Network error for logining in trilium server in trilium-sender

Magic-King opened this issue 2 years ago · comments

I can't login in trilium server in trilium-sender downloaded by google play.
It shows me the network error after I input the necessary info.

And I found logs below, I want to know if there is a script which supported the trilium-sender.

Error: Router not found for request /api/sender
    at /usr/src/app/src/app.js:71:17
    at Layer.handle [as handle_request] (/usr/src/app/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/usr/src/app/node_modules/express/lib/router/index.js:323:13)
    at /usr/src/app/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/usr/src/app/node_modules/express/lib/router/index.js:341:12)
    at next (/usr/src/app/node_modules/express/lib/router/index.js:275:10)
    at Layer.handle [as handle_request] (/usr/src/app/node_modules/express/lib/router/layer.js:91:12)
    at trim_prefix (/usr/src/app/node_modules/express/lib/router/index.js:323:13)
    at /usr/src/app/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/usr/src/app/node_modules/express/lib/router/index.js:341:12) {
  status: 404
}

zadam · Answer 1 · Tue Jan 25 2022 04:32:48 GMT+0800 (China Standard Time)

Hi, there's no extra script or anything needed. Trilium Sender should work out of the box.

Are you sure you're configuring the correct URL/port? I'm not sure what that error means, /api/sender does not exist and is not called by Trilium Sender (but there's e.g. /api/sender/login and other services).

Magic · Answer 2 · Tue Jan 25 2022 10:37:21 GMT+0800 (China Standard Time)

Today I try to read the source code and use android logcat to find out what causes it.
I found that http transport is not supported higher than android 9, and I think this is the key problem.

$ adb logcat |grep UserLoginCoroutine
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: Can't connect to Trilium server
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: java.net.UnknownServiceException: CLEARTEXT communication to my_server not permitted by network security policy
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:188)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:226)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:106)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:74)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:255)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at okhttp3.internal.connection.RealCall.execute(RealCall.kt:154)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at io.github.zadam.triliumsender.LoginActivity$doLogin$2.invokeSuspend(LoginActivity.kt:173)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:738)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
01-25 10:30:11.663 25101 26313 E UserLoginCoroutine: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)

zadam · Answer 3 · Wed Jan 26 2022 03:43:35 GMT+0800 (China Standard Time)

Oh, I see, fix for that has been actually already merged in #18 but not yet released.

morfismo · Answer 4 · Thu Jun 23 2022 12:50:12 GMT+0800 (China Standard Time)

Oh, I see, fix for that has been actually already merged in #18 but not yet released.

Is there a way to get a preview? This is a show stopper on Android.

mtklar · Answer 5 · Thu Aug 18 2022 18:54:03 GMT+0800 (China Standard Time)

Oh, I see, fix for that has been actually already merged in #18 but not yet released.

Is there a way to get a preview? This is a show stopper on Android.

Any news about it?

e-p-s · Answer 6 · Sat Aug 20 2022 00:39:35 GMT+0800 (China Standard Time)

Oh, I see, fix for that has been actually already merged in #18 but not yet released.

Is there a way to get a preview? This is a show stopper on Android.

Any news about it?

+1
No Update since Jan?
Perhaps it's a dead horse and we must use obsidian?
I've just migrated from DS Note and i miss the nativ app badly.

zadam · Answer 7 · Sun Aug 21 2022 04:49:33 GMT+0800 (China Standard Time)

Releases to this app (meaning specifically the android version) are done rarely, as it's quite time-consuming. There has to be a strong driver/reason to make a release, using unsecure HTTP did not do it for me yet.

Wouter Leistra · Answer 8 · Sat Sep 24 2022 18:17:55 GMT+0800 (China Standard Time)

i cannot use the android app because of this issue. It simply won't connect to my self hosted trilium server. Desktop app syncs fine with the same settings. Also it asks for username and the Desktop app doesn't, I would not know what to enter there so i just wrote there trilium.

r-nd-m · Answer 9 · Sun Dec 04 2022 14:16:12 GMT+0800 (China Standard Time)

Same for me - wanted to integrate sending scans from the phone to my Trilium workflow - I get this error when trying to connect to the home server.

Pupo1 · Answer 10 · Mon Dec 19 2022 01:38:32 GMT+0800 (China Standard Time)

I would like a lot to use the app but have the same problem.
Is there a workaround?

Ashthos · Answer 11 · Fri Feb 03 2023 04:31:08 GMT+0800 (China Standard Time)

In case anyone else is still getting this issue, I had the same when my Trilium server (using the Unraid docker package) wasn't the latest version. Make sure the server is pulling the zadam/trilium:0.58.7 version and the login works as expected.

I added my name as the username, as the app won't let you login without providing one (even though Trilium only requires a password).

Edit: I am running the server on http:8080, but using nginx reverse proxy to expose the server on an https endpoint with a valid letsencrypt ssl certificate.

Wouter Leistra · Answer 12 · Fri Feb 03 2023 13:05:35 GMT+0800 (China Standard Time)

Is https required to make it work. I'm still getting network error

contributor · Answer 13 · Sat Apr 29 2023 19:43:38 GMT+0800 (China Standard Time)

Releases to this app (meaning specifically the android version) are done rarely, as it's quite time-consuming

@zadam what about building apk and creating github release? without google play and other stores?

APA Devices · Answer 14 · Fri Jun 30 2023 17:42:48 GMT+0800 (China Standard Time)

I can't go through this issue. Any hint? I also plead for the apk.

HyperCriSiS · Answer 15 · Fri Oct 06 2023 01:03:34 GMT+0800 (China Standard Time)

I also have this issue.
Actually I am using Trilium with Hermit as a Lightapp.
That's not optimal but better than nothing.

John Tirelli · Answer 16 · Mon Jan 01 2024 23:25:18 GMT+0800 (China Standard Time)

Releases to this app (meaning specifically the android version) are done rarely, as it's quite time-consuming. There has to be a strong driver/reason to make a release, using unsecure HTTP did not do it for me yet.

Happy new year, I love trilium. It would seem that it is being included on a number of server management platforms, some of which don't offer ssl solutions out of the box.

I don't really care about ssl, I'm running this on my local network and I only ever access it locally, by IP address, so I know I'm connecting to the right place.

I've successfully built this locally and side-loaded the debug version of the apk, so I can now successfully send notes to my server. I'd like to hear more about the pain points of this project and see if I can help. I'd be happy to try to help set up some workflows to automate the build process, maybe with tagging to get this on f-droid as I've seen in other requests.

matt wilkie · Answer 17 · Mon Apr 15 2024 07:13:55 GMT+0800 (China Standard Time)

@j-tirelli following up in the Trilium Next Sender fork might see more traction: https://github.com/TriliumNext/trilium-sender

I've never built an APK but am happy to help with testing and documentation. Please ping me if you do continue over there.