# Dropbox Uncaught Exception

**URL:** https://discourse.nodered.org/t/dropbox-uncaught-exception/81960
**Category:** General
**Tags:** docker
**Created:** [12 October 2023 08:29 UTC](https://discourse.nodered.org/t/dropbox-uncaught-exception/81960 "2023-10-12T08:29:50Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Josov](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/josov/32/6228_2.png) [@Josov](https://discourse.nodered.org/u/Josov)
#### Post date: [12 October 2023 08:29 UTC](https://discourse.nodered.org/t/dropbox-uncaught-exception/81960/1 "2023-10-12T08:29:50Z")

</div>

Since about a week Node-RED keeps on restarting due an uncaught exception in node-red-node-dropbox, before there were no issues. I created a new access code and a new refresh token but it does not help. Currently 4 Raspberry Pi's use the same Dropbox access code and refresh token. Node-RED is running in a Docker environment. Any idea's how to resolve this issue?

 ![afbeelding](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/7/4791718f7f20421d29bfb752de660b9db4b8182e.png)

---

<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: [11 December 2023 08:30 UTC](https://discourse.nodered.org/t/dropbox-uncaught-exception/81960/2 "2023-12-11T08:30:07Z")

</div>

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