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

(Telegram) Notification broken (in docker)? #377

Open
silentguy256 opened this issue Sep 6, 2024 · 6 comments
Open

(Telegram) Notification broken (in docker)? #377

silentguy256 opened this issue Sep 6, 2024 · 6 comments

Comments

@silentguy256
Copy link

silentguy256 commented Sep 6, 2024

as we know epic hasn't worked for ages for me but I kind of still have it running once a week for other services and as a reminder to manually check in... A while ago notifications via telegram broke:

fgc  |
fgc  | --- Exception:
fgc  | Error: Command failed: apprise 'tgram://XXX:YYY/ZZZ' -i html -b 'epic-games: no longer signed in and not enough options set for automatic log in.'
fgc  |
fgc  |     at genericNodeError (node:internal/errors:984:15)
fgc  |     at wrappedFn (node:internal/errors:538:14)
fgc  |     at ChildProcess.exithandler (node:child_process:422:12)
fgc  |     at ChildProcess.emit (node:events:519:28)
fgc  |     at maybeClose (node:internal/child_process:1105:16)
fgc  |     at ChildProcess._handle.onexit (node:internal/child_process:305:5)
fgc  |     at Process.callbackTrampoline (node:internal/async_hooks:130:17) {
fgc  |   code: 1,
fgc  |   killed: false,
fgc  |   signal: null,
fgc  |   cmd: "apprise 'tgram://XXX:YYY/ZZZ' -i html -b 'epic-games: no longer signed in and not enough options set for automatic login.'"
fgc  | }
fgc  | error: Command failed: apprise 'tgram://XXX:YYY/ZZZ' -i html -b 'epic-games failed: Command failed: apprise 'tgram://XXX:YYY/ZZZ' -i html -b 'epic-games: no longer signed in and not enough options set for automatic login.''
fgc  |
fgc  | node:internal/errors:984
fgc  |   const err = new Error(message);
fgc  |               ^
fgc  |
fgc  | Error: Command failed: apprise 'tgram://XXX:YYY/ZZZ' -i html -b 'epic-games failed: Command failed: apprise 'tgram://XXX:YYY/ZZZ' -i html -b 'epic-games: no longer signed in and not enough options set for automatic login.''
fgc  |
fgc  |     at genericNodeError (node:internal/errors:984:15)
fgc  |     at wrappedFn (node:internal/errors:538:14)
fgc  |     at ChildProcess.exithandler (node:child_process:422:12)
fgc  |     at ChildProcess.emit (node:events:519:28)
fgc  |     at maybeClose (node:internal/child_process:1105:16)
fgc  |     at ChildProcess._handle.onexit (node:internal/child_process:305:5)
fgc  |     at Process.callbackTrampoline (node:internal/async_hooks:130:17) {
fgc  |   code: 1,
fgc  |   killed: false,
fgc  |   signal: null,
fgc  |   cmd: "apprise 'tgram://XXX:YYY/ZZZ' -i html -b 'epic-games failed: Command failed: apprise 'tgram://XXX:YYY/ZZZ' -i html -b 'epic-games: no longer signed in and not enough options set for automatic login.''"
fgc  | }

Manually triggering "apprise 'tgram://XXX:YYY/ZZZ' -i html -b 'epic-games: no longer signed in and not enough options set for automatic login.'", which i copy pasted from the error, works fine

@vogler
Copy link
Owner

vogler commented Sep 6, 2024

I had that problem once as well. Reinstalled apprise and it worked again. How did you install it? brew/apt/pip/pipx...?
Maybe your $PATH is different for an interactive shell which is why it finds apprise there.
Check type apprise to see if it's in multiple places. You can run env -i bash to get a shell without any env vars inherited, and then try to run the command from above with an absolute path to apprise to see if that works.

@silentguy256
Copy link
Author

Hm, I'm just running the docker container, usually just with "docker compose up -d" and to test it I ran it with "docker compose run free-games-claimer apprise 'tgram://..."

Starting the container not running the scripts but bash instead apprise is only in one location and it always works when called manually, with or without absolute path, also both from within env -i bash 🤷‍♂️

@vogler
Copy link
Owner

vogler commented Sep 6, 2024

Ah, ok, then it's something else. Are you running the latest image? Haven't changed anything involving apprise recently (although, could be that the apprise version changed between builds). If it's broken, it should be broken for everyone using the image.

@silentguy256
Copy link
Author

I am on the current image now, but diagnosing when the happens is a bit difficult because at first I thought I'd just check when it stopped working, which was two weeks ago, but then I noticed that that was when I was doing some maintenance to the server running it, so in theory that could be directly related, but probably that's just when I did a docker compose pull for this program, which I did not do regularly, because I thought the fact that no new releases on here ment no new docker containers...
So it could possibly be related to the last change to apprise escaping 3 months ago, but it would surprise me if no one else noticed it since then...

@Elmagenta
Copy link

I have a similar problem with gotify too, i'm also using the latest image.
Gotify server is working cause i receive notification from other services that i use.

Error: Command failed: apprise 'gotify://myip' ... (Didn't know what to cancel here so i delete all the block, but they were almost all reference to the claimed games)
06/09/2024 14:32:41
    at genericNodeError (node:internal/errors:984:15)
06/09/2024 14:32:41
    at wrappedFn (node:internal/errors:538:14)
06/09/2024 14:32:41
    at ChildProcess.exithandler (node:child_process:422:12)
06/09/2024 14:32:41
    at ChildProcess.emit (node:events:519:28)
06/09/2024 14:32:41
    at maybeClose (node:internal/child_process:1105:16)
06/09/2024 14:32:41
    at ChildProcess._handle.onexit (node:internal/child_process:305:5)
06/09/2024 14:32:41
    at Process.callbackTrampoline (node:internal/async_hooks:130:17) {
06/09/2024 14:32:41
  code: 1,
06/09/2024 14:32:41
  killed: false,
06/09/2024 14:32:41
  signal: null

@silentguy256 silentguy256 changed the title Telegram notification broken? (Telegram) Notification broken (in docker)? Sep 7, 2024
@tobiasdroste
Copy link

My gmail notifications via notify stopped working after upgrading my docker image a few days ago. Didn't change anything else about my setup.

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

No branches or pull requests

4 participants