# NBI exception - Firmware update

**URL:** <https://forum.genieacs.com/t/nbi-exception-firmware-update/1279>\
**Category:** Uncategorized\
**Created:** [December 7, 2020, 12:05pm UTC](https://forum.genieacs.com/t/nbi-exception-firmware-update/1279 "2020-12-07T12:05:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ahamdaoui](https://avatars.discourse-cdn.com/v4/letter/a/e9bcb4/32.png) [@ahamdaoui](https://forum.genieacs.com/u/ahamdaoui)\
**Post date:** [December 7, 2020, 12:05pm UTC](https://forum.genieacs.com/t/nbi-exception-firmware-update/1279/1 "2020-12-07T12:05:03Z")

</div>

Hello everyone,

I’m using GenieACS version 1.2.3 / MongoDB version 4.4 / NodeJS version 14.x

I have this error that happens very randomly when I try to update the firmware (Draytek Vigor2762) via the genieacs API:

genieacs-nbi[4271]: 2020-11-09T14:59:39.524Z [ERROR] Uncaught exception; pid=4300 exceptionName=“SyntaxError” exceptionMessage=“Unexpected token , in JSON at position 27” exceptionStack=“SyntaxError: Unexpected token , in JSON at position 27\n  
at JSON.parse ()\n  
at IncomingMessage. (/usr/lib/node\_modules/genieacs/bin/genieacs-nbi:2:64021)\n  
at IncomingMessage.emit (events.js:327:22)\n  
at endReadableNT (\_stream\_readable.js:1327:12)\n  
at processTicksAndRejections (internal/process/task\_queues.js:80:21)”  
genieacs-nbi[4271]: 2020-11-09T15:00:05.543Z [ERROR] Worker died; pid=6245 exitCode=1  
genieacs-nbi[4271]: 2020-11-09T15:00:05.890Z [INFO] Worker listening; pid=6299 address=“0.0.0.0” port=7557

Curiously, the firmware update is done without any problem!

Thanks in advance for your help.

---

<div class="post-metadata">

**Author:** ![zaidka](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/zaidka/32/9_2.png) [@zaidka](https://forum.genieacs.com/u/zaidka)\
**Post date:** [December 17, 2020, 4:08am UTC](https://forum.genieacs.com/t/nbi-exception-firmware-update/1279/2 "2020-12-17T04:08:33Z")

</div>

Can you share a packet capture of the request that’s triggering this exception?
