# Error with Minio Notification

**URL:** <https://discourse.nodered.org/t/error-with-minio-notification/82155>\
**Category:** General\
**Created:** [18 October 2023 10:03 UTC](https://discourse.nodered.org/t/error-with-minio-notification/82155 "2023-10-18T10:03:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vicente87](https://avatars.discourse-cdn.com/v4/letter/v/db5fbb/32.png) [@vicente87](https://discourse.nodered.org/u/vicente87)\
**Post date:** [18 October 2023 10:03 UTC](https://discourse.nodered.org/t/error-with-minio-notification/82155/1 "2023-10-18T10:03:34Z")

</div>

I am using this node (contrib-minio-all, specifically the notifications node) in a project where I am testing the puts that are made to a certain Minio bucket. And suddenly node-red stops working and then it won't let me relaunch it.  
The error I get is the following:18 Oct 11:51:36 - [info] Starting flows  
18 Oct 11:51:37 - [info] Started flows  
{  
objectCreated: {  
put: false,  
post: false,  
copy: false,  
completeMultipartUpload: true  
},  
objectRemovedDelete: false,  
objectAccessed: { get: false, head: false },  
listenerStop: undefined  
}  
{  
objectCreated: {  
put: false,  
post: true,  
copy: false,  
completeMultipartUpload: false  
},  
objectRemovedDelete: false,  
objectAccessed: { get: false, head: false },  
listenerStop: undefined  
}  
18 Oct 11:51:37 - [red] Uncaught Exception:  
18 Oct 11:51:37 - [error] S3Error: Access Denied.  
at parseError (/root/.node-red/node\_modules/minio/dist/main/internal/xml-parser.js:35:13)  
at Object.parseResponseError (/root/.node-red/node\_modules/minio/dist/main/internal/xml-parser.js:82:11)  
at process.processTicksAndRejections (node:internal/process/task\_queues:95:5)  
at async Client.makeRequestStreamAsync (/root/.node-red/node\_modules/minio/dist/main/internal/client.js:476:19)

If anyone could help me or give me some clue as to what is going on.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [18 October 2023 10:41 UTC](https://discourse.nodered.org/t/error-with-minio-notification/82155/2 "2023-10-18T10:41:22Z")

</div>

`Access Denied` whilst using the API, and the node is not handling it correctly - causing Node RED to crash - you will need to raise this with the node author

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [18 October 2023 10:47 UTC](https://discourse.nodered.org/t/error-with-minio-notification/82155/3 "2023-10-18T10:47:42Z")

</div>

If you are using [node-red-contrib-minio-all](https://flows.nodered.org/node/node-red-contrib-minio-all) you should notice that it says:

`Please Note: This set of nodes (and associated support information) is a work in progress.`

and it hasn't been update in over two years.

You could open an issue on the node's GitHub page however the author(s) don't seem to be answering questions or maintaining the node so you might want to explore other ways to do what you are trying to do.

---

<div class="post-metadata">

**Author:** ![vicente87](https://avatars.discourse-cdn.com/v4/letter/v/db5fbb/32.png) [@vicente87](https://discourse.nodered.org/u/vicente87)\
**Post date:** [18 October 2023 11:15 UTC](https://discourse.nodered.org/t/error-with-minio-notification/82155/4 "2023-10-18T11:15:40Z")

</div>

I will change to another type of node that provides more stability.  
Thank you so much.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [17 December 2023 11:15 UTC](https://discourse.nodered.org/t/error-with-minio-notification/82155/5 "2023-12-17T11:15:57Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.