Dappnode core v0.3.5 "Not signed" and "unsafe origin, bad signature"

Problem

I'm trying to update my Dappnode software. I see these concerning warnings for Dappnode core 0.3.5

Hmm that doesnt make sense, because the Core release is properly signed. I just updated without issue, and the releases were signed. What i don't get is why there are apparently 4 signed packages, and one not, making 5 total packages in this update.
if youve been keeping up to date, this update should have at most 3 updates: Dappmanager, Core (those 2 go together), and Notifications; just because of when it was released shortly before the new Core, auto updates wouldnt have installed notifications before the new core was relesaed. due to the 24 hour delay built in to auto updates.

Please post your currently installed software versions, from here
Please also post your Release Trusted Keys list from this page
Should give a lot more context because theres not an issue with the core release's signature, its an issue on your node's end. So more info is needed to troubleshoot your issue.

Right now I assume you are far behind on updates just given the screenshots ive seen so far, and to resolve that well likely need to update some of them manually and not bundle it all in one, which can create issues on its own

Right now I assume you are far behind on updates just given the screenshots ive seen so far, and to resolve that well likely need to update some of them manually and not bundle it all in one, which can create issues on its own

I have auto updates enabled for system packages so not sure how this happened.

I tried to manually update again and I'm hitting more errors

@pablomendezroyo

Ok so yeah it appears you are umm very far behind, youre missing the keys that would solve the signature issues because youre on a pretty old Core 6 versions ago from 3 months ago. This is your issue its the source of all your signature issues and im surprised its not causeing like a lot more issues since you have such old dappnode software, also you could use an update to your docker install, but again im not sure the best way to resolve this off hand. Personally i would probably just bypass all the signature issues to see if it installs all the latest, but i think because youre so far behind you may need to upgrade to an old core (newer than yours but older than current, because i beleive there were migrations included in one of those updates, so skipping past them could be really bad.

@pablomendezroyo can you assist this user in getting properly caught up to current software versions hes still on core 0.2.105 and has a ton of very old outdated core packages not updated due to a core update needing to be done manually. I just want to make sure whatever Core version(s) that had migrations involved isnt skipped as he gets his node up to the latest releases, since hes 3 months and 6 core versions behind, and cant upgrade due to lacking the new keys added to the trusted store, and idk when that was implemented etc. Thanks!

I tried to update core with "Bypass only signed safe restriction" and hit

When I click show details, it showed me an empty support page. I eventually found these logs

Error: Command failed: docker compose -f /usr/src/app/DNCORE/docker-compose-bind.yml config <&-
validating /usr/src/app/DNCORE/docker-compose-bind.yml: services.bind.dnp.dappnode.eth.networks.dncore_network.ipv4_address must be a string

    at shell (file:///usr/src/app/packages/utils/dist/shell.js:30:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async writeAndValidateFiles (file:///usr/src/app/packages/installer/dist/installer/writeAndValidateFiles.js:24:9)
    at async packageInstall (file:///usr/src/app/packages/installer/dist/calls/packageInstall.js:59:13)
    at async packageInstall (file:///usr/src/app/packages/dappmanager/dist/calls/packageInstall.js:19:5)
    at async file:///usr/src/app/packages/dappmanager/dist/api/handler/index.js:24:28

{
  "name": "core.dnp.dappnode.eth",
  "version": "0.3.5",
  "userSettings": {},
  "options": {
    "BYPASS_SIGNED_RESTRICTION": true
  }
}

Any updates on this ?

@rootulp

Problem

I'm trying to update my Dappnode software. I see these concerning warnings for Dappnode core 0.3.5

@rootulp hey! so regarding the"Not Signed" issue, we will release today core v0.3.9, which you should be able to update with no issues

I tried to update core with "Bypass only signed safe restriction" and hit

When I click show details, it showed me an empty support page. I eventually found these logs

Error: Command failed: docker compose -f /usr/src/app/DNCORE/docker-compose-bind.yml config <&-
validating /usr/src/app/DNCORE/docker-compose-bind.yml: services.bind.dnp.dappnode.eth.networks.dncore_network.ipv4_address must be a string

    at shell (file:///usr/src/app/packages/utils/dist/shell.js:30:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async writeAndValidateFiles (file:///usr/src/app/packages/installer/dist/installer/writeAndValidateFiles.js:24:9)
    at async packageInstall (file:///usr/src/app/packages/installer/dist/calls/packageInstall.js:59:13)
    at async packageInstall (file:///usr/src/app/packages/dappmanager/dist/calls/packageInstall.js:19:5)
    at async file:///usr/src/app/packages/dappmanager/dist/api/handler/index.js:24:28

{
  "name": "core.dnp.dappnode.eth",
  "version": "0.3.5",
  "userSettings": {},
  "options": {
    "BYPASS_SIGNED_RESTRICTION": true
  }
}

Regarding this issue you must run the following command in the CLI, let me know if it fixes your issue

docker compose -f /usr/src/dappnode/DNCORE/docker-compose-bind.yml config <&- 2>&1 \
  | grep -q 'ipv4_address must be a string' \
  && { echo "Warning: docker‑compose‑bind.yml is corrupted – forcing dncore_network.ipv4_address to 172.33.1.2…"; \
       sudo sed -i -E 's/^([[:space:]]*)ipv4_address:.*$/\1ipv4_address: 172.33.1.2/' /usr/src/dappnode/DNCORE/docker-compose-bind.yml; }

Thanks, I ended up manually quoting the IP in Bind YML which fixed it! I see the command basically does the same thing

This did not work for me. When I go to update the address and put it in string format, the updater just overwrites it? Also, the above sed command doesn't look like its quoting and it also looks like it is the wrong path. The file is located at /usr/src/app/DNCORE/docker-compose-bind.yml.

This did not work for me. When I go to update the address and put it in string format, the updater just overwrites it? Also, the above sed command doesn't look like its quoting and it also looks like it is the wrong path. The file is located at /usr/src/app/DNCORE/docker-compose-bind.yml.

I got past this eventually by:

ssh to the host
running "docker exec -it <dapp_manager_container_id> /bin/sh" to open a shell.
cd DNCORE
vi docker-compose-bind.yml
Add quotes to the IP (I used single)
cp docker-compose-bind.yml docker-compose-bind.yml.correct
Run:

while `true`; do
cp docker-compose-bind.yml.correct docker-compose-bind.yml
done

Then retry the install.

This is a rather absurd way of doing things and I wonder whether the file could be half-read at any point. However, it did work first time.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

Navigation Menu

Repository navigation

Dappnode core v0.3.5 "Not signed" and "unsafe origin, bad signature" #663

Problem

Problem

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Dappnode core v0.3.5 "Not signed" and "unsafe origin, bad signature" #663

Description

Problem

Activity

alexpeterson91 commented on Jul 24, 2025

rootulp commented on Jul 24, 2025

rootulp commented on Jul 24, 2025

alexpeterson91 commented on Jul 24, 2025

rootulp commented on Jul 25, 2025

ArunSankarKs commented on Sep 5, 2025

pablomendezroyo commented on Sep 5, 2025

Problem

pablomendezroyo commented on Sep 5, 2025

ArunSankarKs commented on Sep 9, 2025

astralbat commented on Oct 24, 2025

astralbat commented on Dec 9, 2025

stale commented on Mar 8, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions