Apprise URL not working

[p-jones]

Checklist

• I have read the docs.
• I have searched open and closed issues.

Deployment Environment

Docker Compose

Description

I have my Apprise instance up and running, and I have tested Telegram notifications and everything works via Apprise.

I have Apprise running on a VM, not the same one as my Speedtest instance. The Apprise URL is http://192.168.50.98:8000. So, in Speedtest, I appended "/notify" to it (http://192.168.50.98:8000/notify). But every time I try to get a notification in Speedtest, I get an error: "Failed to send Apprise test notification. Apprise returned an error, please check Apprise logs for details". The Speedtest log doesn't have any info there.

Any help is appreciated!

Anything else?

No response

[svenvg93]

Did you check the apprise logs as the error suggested 😅. There should be a indication why it refused the message. As we got an error returned by apprise.

[p-jones]

Thank you for the reply and sorry for having missed the nuance of checking the wrong app's logs. I have not received an obvious error when inspecting the Apprise logs.

I did get the following:
[pid: 151|app: 0|req: 12/15] 192.168.50.66 () {36 vars in 1297 bytes} [Sat Dec 27 13:36:08 2025] GET /status => generated 155 bytes in 1 msecs (HTTP/1.1 200) 6 headers in 366 bytes (1 switches on core 0)

but it is not obvious to me what might be wrong.

I have re-confirmed Apprise itself is functioning correctly.

Could my Service URL in Speedtest be wrong? I am using:

tgram://{telegram token}/{chat id}

Thanks again.

[svenvg93]

No worries, Apprise has different errors it can return. Hence we refer to the apprise logs them self.

The log shown is for when requesting /status which is an internal apprise endpoint and doesn’t tell us much. We need the log line after sending the test notification form the Speedtest tracker for example.

For using telegram check out https://github.com/caronc/apprise/wiki/Notify_telegram for more information.

[andylee-ca]

I'm also having issues with this and found this thread. The instructions were a little confusing but I've tried my best to to infer.

Apprise Server URL* : http://192.168.1.160:8001/notify

I'm not certain about this one. The hint said URL should end with notify, but syntax should be http://192.168.1.160:8001/notify/KEY where KEY is the config ID. I've tried both with or without KEY; no luck.

I'm also not sure what Service URL* should be. The hint suggests it should be discord://WebhookID/Token, but that should have already been declared in Apprise's configuration (http://192.168.1.160:8001/cfg/KEY) and controlled using KEY and tags attributes. Nevertheless, I've copied my discord://WebhookID/Token into the field; no luck.

"Test Apprise" returned "Apprise Server URL is not configured Please configure the Apprise Server URL in the settings above."

Apprise log shows no new entries immediately after "Test Apprise", so I'm not even sure that test reached Apprise.

I'm out of ideas.

Edit: I've configured unraid, emby, a bunch of -arr using Apprise and all of those worked.

Edit2: Read another thread, looks like this feature might not be fully implemented yet.

[svenvg93]

At the moment we don't support tags yet we are working on adding support for this, see #2503 . For now it's only a stateless configuration that is supported. Hence why the URL need end on /notify and the service url need to be provided.

As for the error in the test notification, you need to save the settings first before it works. This will be improved in the next release.

[andylee-ca]

Thank you! Saved and notifications working now. I didn't notice the save button tucked away three folds down at the very bottom.

Yup, i saw #2503 hence the Edit 2.

[svenvg93]

I didn't notice the save button tucked away three folds down at the very bottom.

Yeah its s bit hidden now, the admin panel shows it only at the bottom of the page. Once we remove the deprecated channels from the page it will more visible.