Closed ostasevych closed 2 months ago
Error 403 (Forbidden) generally implies you either put the wrong user/password in.
If your password contains a lot of mixed characters, you could try putting it on the URL instead such as:
nclouds://mydomain.tld/master?user=myaccount&password=mypassword
The other alternative is to escape your special characters (see here)
Error 403 (Forbidden) generally implies you either put the wrong user/password in.
If your password contains a lot of mixed characters, you could try putting it on the URL instead such as:
nclouds://mydomain.tld/master?user=myaccount&password=mypassword
The other alternative is to escape your special characters (see here)
the thing is that the password is generated by the nextcloud itself, so it consists of several digits of ABC symbols split by "-". Nothing else.
Looking through the documentation that is part of the NextCloud library, i don't see anything out of the ordinary. Does your master
user have admin
privileges?
Looking through the documentation that is part of the NextCloud library, i don't see anything out of the ordinary. Does your
master
user haveadmin
privileges?
yes, it has, however specifically this account is disabled now. Should it be active in order the service can work?
Same problem here, while using apprise within uptime-kuma
2024-01-26T16:14:11+01:00 [MONITOR] ERROR: Cannot send notification to Nextcloud Talk
Error: Process exited with code 1
at ChildProcess.done (/app/node_modules/promisify-child-process/index.cjs:70:19)
at ChildProcess.emit (node:events:517:28)
at maybeClose (node:internal/child_process:1098:16)
at ChildProcess._handle.onexit (node:internal/child_process:303:5) {
code: 1,
signal: null,
stdout: '2024-01-26 16:14:11,238 - WARNING - Failed to send Nextcloud Talk notification:error=403.\n',
stderr: ''
}
Authentication is working as Nextcloud shows activity for App password
I had a look here and it says the following:
Seems that the topic is read-only
, is that possible?
Sorry @caronc .. this was the problem.. Thanks!!!
I'll leave this ticket open. I can improve on the error message being displayed to make this kind of thing more obvious in the future
I have checked with another user, trying to send a notification to myself. The command was executed on the webserver directly.
apprise -vvvvv -t "title" -b "body" nclouds://myuser:ABCD-EFG-HIJ-KLM@my.local/myuser
Getting the same error.
This is what I see in /var/log/apache2/nextcloud.access
file:
***.***.***.*** - myuser [16/Apr/2024:00:56:27 +0300] "GET /ocs/v2.php/apps/notifications/api/v2/notifications?format=json HTTP/1.1" 304 3076 "-" "Mozilla/5.0 (Windows) mirall/3.12.3stable-Win64 (build 20240328) (Nextcloud, windows-10.0.19045 ClientArchitecture: x86_64 OsArchitecture: x86_64)"
***.***.***.*** - myuser [16/Apr/2024:00:56:28 +0300] "PROPFIND /remote.php/dav/files/myuser/ HTTP/1.1" 207 1193 "-" "Mozilla/5.0 (Windows) mirall/3.12.3stable-Win64 (build 20240328) (Nextcloud, windows-10.0.19045 ClientArchitecture: x86_64 OsArchitecture: x86_64)"
127.0.0.1 - myuser [16/Apr/2024:00:56:35 +0300] "POST //ocs/v2.php/apps/notifications/api/v2/admin_notifications/myuser HTTP/1.1" 403 3946 "-" "Apprise"
NC 27.1.8
Several thoughts: short name of my domain, which is private, self-signed, and consists of 2 words; I use 2FA (the password is created for a specific device). I've tried to remove password, change it, however the error remains the same:
So, with the command
apprise -vvvvv -t "title" -b "body" nclouds://myuser:ABCD-EFG-HIJ-KLM@my.local/myuser
I am getting this trace error:
2024-04-16 01:10:47,100 - DEBUG - Loaded Nextcloud URL: nclouds://myuser:****@my.local/myuser?version=21&format=text&overflow=upstream&rto=4.0&cto=4.0&verify=yes
2024-04-16 01:10:47,100 - DEBUG - Nextcloud v21 POST URL: https://a3.local//ocs/v2.php/apps/notifications/api/v2/admin_notifications/myuser (cert_verify=True)
2024-04-16 01:10:47,100 - DEBUG - Nextcloud v21 Payload: {'shortMessage': 'title', 'longMessage': 'body'}
2024-04-16 01:10:47,359 - WARNING - Failed to send Nextcloud v21 notification:error=403.
2024-04-16 01:10:47,361 - DEBUG - Response Details:
b''
Sorry, I found the issue, the local IP address wasn't in the list of allowed to be logged in! Everything works from now.
Hi! I am trying to configure the nextcloud notification.
I've added app password and run the command:
Getting the 403 error:
What may be wrong?