Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error sending request for url #72

Open
deadcombo opened this issue Jan 14, 2025 · 1 comment
Open

Error sending request for url #72

deadcombo opened this issue Jan 14, 2025 · 1 comment

Comments

@deadcombo
Copy link

deadcombo commented Jan 14, 2025

root@d5ebaa6ce3e6:/data# RUST_BACKTRACE=full mollysocket connection ping [redacted]
[2025-01-14T12:01:37Z INFO  mollysocket::config] No config file supplied
[2025-01-14T12:01:37Z INFO  mollysocket::vapid] VAPID public key: "[redacted]"
thread 'main' panicked at src/cli/connection.rs:125:28:
called `Result::unwrap()` on an `Err` value: error sending request for url ([redacted]/up[redacted]?up=1)

Caused by:
   0: client error (Connect)
   1: tcp connect error: Connection refused (os error 111)
   2: Connection refused (os error 111)

Location:
    src/utils/post_allowed.rs:106:8
stack backtrace:
   0:     0xaaaae45a4164 - <unknown>
   1:     0xaaaae43ec058 - <unknown>
   2:     0xaaaae457d518 - <unknown>
   3:     0xaaaae45a4e04 - <unknown>
   4:     0xaaaae45a5344 - <unknown>
   5:     0xaaaae45a4ec4 - <unknown>
   6:     0xaaaae45a4e3c - <unknown>
   7:     0xaaaae45a4e30 - <unknown>
   8:     0xaaaae430004c - <unknown>
   9:     0xaaaae43002b8 - <unknown>
  10:     0xaaaae436d3d4 - <unknown>
  11:     0xaaaae439e2d4 - <unknown>
  12:     0xaaaae432a778 - <unknown>
  13:     0xaaaae439fc4c - <unknown>
  14:     0xffff8d7b7740 - <unknown>
  15:     0xffff8d7b7818 - __libc_start_main
  16:     0xaaaae4310530 - <unknown>
  17:                0x0 - <unknown>

This is running in a container using the docker-compose file.

Not entirely sure this is a crash or the server really can’t reach my ntfy instance. I've double checked the endpoint URL and set write access for everyone in order to debug this. I can use ntfy just fine with schildichat and just posting my own notifications.

@p1gp1g
Copy link
Member

p1gp1g commented Jan 14, 2025

Can you try to curl you ntfy server from your mollysocket container ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants