search

FliegendeWurst / telegram_notes_bot

Telegram bot that saves notes and reminders (integrated with Trilium Notes)
GNU Affero General Public License v3.0
5 stars 0 forks source link

Clarification about the #1

Closed mondayrobot closed 3 years ago

mondayrobot commented 3 years ago

Hello, Thanks for this, it will be really useful! I followed all your instructions, but at the last step I get the error below. Can you please help? Thanks!

Loading configuration..
Initializing Telegram API..
Initializing Trilium API..
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Ipv4(xxxxxxx)), port: Some(xx), path: "/api/login/token", query: None, fragment: None }, source: hyper::Error(Parse(Version)) }', src/lib.rs:42:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
FliegendeWurst commented 3 years ago

That's a really strange error! Is the sync server running properly? Did you set up HTTPS (the bot currently only expects http)?

You can also try the latest commit, I just updated some dependencies and fixed a (different) issue in the initialization code.

mondayrobot commented 3 years ago

Thank you for your help and sorry about double posting. Yes, I set up HTTPS, so that might be the issue. Is there something I can do to troubleshoot that? The server sync is running well.

FliegendeWurst commented 3 years ago

Previously, HTTP was specified explicitly in the source code. I have now changed it so you can also use a HTTPS host (see the updated readme).

mondayrobot commented 3 years ago

Hi,

Thanks for your fast update! I still have an error, you'll find the details below. Just to add that I'm not a very technical profile, so maybe there is a problem on how I configured things. So it would be OK if you close the issue and don't loose your time anymore on it.

Loading configuration..
Initializing Telegram API..
Initializing Trilium API..
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Request, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("my.domain.xxx")), port: Some(22), path: "/api/login/token", query: None, fragment: None }, source: hyper::Error(Connect, Custom { kind: Other, error: Custom { kind: InvalidData, error: CorruptMessage } }) }', src/lib.rs:42:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: JoinError::Panic(...)', src/main.rs:24:14
FliegendeWurst commented 3 years ago

Looking at the error hyper::Error(Connect, Custom { kind: Other, error: Custom { kind: InvalidData, error: CorruptMessage } }) I don't think the issue is related to the bot, it could be a bug in hyper (the HTTP library) or the trilium server..