Failed to send Nextcloud notification:Page not found., error=404

[leon1995]

❓ Question
Hi,

when using apprise with nextcloud, I get the following errors:

$ apprise -vv -t "Test Message Title" -b "Test Message Body" nclouds://admin:<censored>@<censored>/<username>
2021-06-02 14:47:01,612 - INFO - Notifying 1 service(s) asynchronously.
2021-06-02 14:47:02,311 - WARNING - Failed to send Nextcloud notification:Page not found., error=404.

I have notifications installed on my nextcloud (version 21.0.2) and used an app-password without filesystem access.

Do you have any suggestion how I can fix it?

[amitsax]

Is you nextcloud instance installed as nextcloud.example.com or example.com/nextcloud -- i.e. as direct domain (or sub-domain) or as subfolder?

[leon1995]

It is directly installed as sub-domain, e.g. cloud.example.com

[amitsax]

It is directly installed as sub-domain, e.g. cloud.example.com

ok.. I got the similar error "Failed to send Nextcloud notification:Page not found., error=404." but I am using nextcloud in a subfolder structure, so I suspect that might be throwing apprise off in my case.

[leon1995]

Ok thx for the info. Sadly, this is not why its not working for me.

[PhilippHomann]

I also just stumpled on that.
Nextcloud decided to change the API URL...
https://github.com/nextcloud/notifications/blob/2d86327752d34f0b4c26826d77e1dffc31daa296/docs/admin-notifications.md#http-request

[caronc]

Hi guys, the accompanying issue to this is #371.

It seems like Next Cloud changed their API for a version and then changed it back in the master branch.

I"m not sure if you want me to patch Apprise so that it accommodates just v21 (of Next Cloud), but then acts the normal way for <= v21 and >= v22? See here for the issue

Thoughts?

[caronc]

It's been about a month now; do you guys want me to keep this ticket open and do anything? I'm almost tempted to let Nextcloud get their version fixed and add in the documentation that Apprise won't work with V21. Not sure if a lot of if/else overhead should be written int the Apprise code to handle an upstream error. But this is always still an option.

I'll close this ticket in another week if i don't hear anything back.

[caronc]

Just closing this ticket since there has been no further feedback. Please feel free to open another ticket if you still have any questions or concerns.

[amitsax]

Just a note, for those with 404 error; if you are using LDAP for user authentication check your intended username where you intend to send the message at: https:///settings/users
it may be a big string of UUID instead of your 'login id'.

also with "/?version=nn" fix - new NC versions =>21 are working now with #432 . Wiki does not have details of that variable yet.

[caronc]

Great point @amitsax ! Fixed

[jamincollins]

if you are using LDAP for user authentication check your intended username where you intend to send the message at: https:///settings/users
it may be a big string of UUID instead of your 'login id'

HUGE thank you! This should likely be mentioned in the documentation.