# Node not working after update

**URL:** <https://forum.storj.io/t/node-not-working-after-update/28498>\
**Category:** troubleshooting\
**Tags:** docker, synology-nas\
**Created:** [November 11, 2024, 9:40am UTC](https://forum.storj.io/t/node-not-working-after-update/28498 "2024-11-11T09:40:21Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![julez](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/julez/32/66_2.png) [@julez](https://forum.storj.io/u/julez)\
**Post date:** [November 12, 2024, 8:12am UTC](https://forum.storj.io/t/node-not-working-after-update/28498/15 "2024-11-12T08:12:42Z")

</div>

Thanks. We’re back up and running. It’s a little embarrassing!

Firstly, no FATAL or Unrecoverable errors. But grepping server address in config.yaml showed that I had commented this out as part of my initial troubleshooting and incorrectly removing some old config entries that were being flagged in config file as invalid in docker logs output:

```auto
|2024-11-10T22:05:48Z|INFO|Invalid configuration file key|{Process: storagenode-updater, Key: storage2.piece-scan-on-startup}|
|---|---|---|---|
|2024-11-10T22:05:48Z|INFO|Invalid configuration file key|{Process: storagenode-updater, Key: retain.concurrency}|
|2024-11-10T22:05:48Z|INFO|Invalid configuration file key|{Process: storagenode-updater, Key: storage2.trust.exclusions}|
|2024-11-10T22:05:48Z|INFO|Invalid configuration file key|{Process: storagenode-updater, Key: server.address}|
|2024-11-10T22:05:48Z|INFO|Invalid configuration file key|{Process: storagenode-updater, Key: storage2.max-concurrent-requests}|

```

I thought I had checked these against the current defaults at: [Config.yaml - Linux/Docker all parameters](https://forum.storj.io/t/config-yaml-linux-docker-all-parameters/24850) but looks like I missed that the server.address was still valid. Still not sure why my docker logs showed the key as invalid previously but not now?

Hopefully I can recover node sufficiently as my online %age has dropped after being off for 36 hours.

Thanks again for your help.

---

_[View the full topic](https://forum.storj.io/t/node-not-working-after-update/28498)._
