You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a remote zerotier controller is setup in ZT Controller -> Controller -> Local ZeroTier URL/Zerotier Secret, setting up a new planet results in the error message
identity.public file does NOT exist, cannot generate planet file.
🔍 Steps to Reproduce
Run ZTNet without the /var/lib/zerotier folder mounted to local ZeroTier
Setup a remote ZeroTier Controller in ZTNet
Create a Planet
🌐 Browser
Chrome
🔧 Deployment Type
Docker
Standalone
✨ Expected Behavior
ZTNet should use the existing entered identity to create the planet
📋 ZTNET Logs
An error occurred while reading the ZT_SECRET
Error: ENOENT: no such file or directory, open '/var/lib/zerotier-one/authtoken.secret'
at Object.readFileSync (node:fs:448:20)
at /app/.next/server/chunks/1875.js:1:6507
at /app/.next/server/chunks/1875.js:1:6633 {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/var/lib/zerotier-one/authtoken.secret'
}
An error occurred while reading the ZT_SECRET
Error: ENOENT: no such file or directory, open '/var/lib/zerotier-one/authtoken.secret'
at Object.readFileSync (node:fs:448:20)
at /app/.next/server/chunks/8108.js:1:2187
at /app/.next/server/chunks/8108.js:1:2313
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/var/lib/zerotier-one/authtoken.secret'
}
Socket is initializing
2024/09/13 01:39:55 startup flag parsed: true
2024/09/13 01:39:55 config file read.
2024/09/13 01:39:55 config file unmarshalled.
2024/09/13 01:39:55 read world signing key failed: open previous.c25519: no such file or directory , open current.c25519: no such file or directory
2024/09/13 01:39:55 preflight check error occurred, but still can proceed.
2024/09/13 01:39:55 new world signing key generated.
2024/09/13 01:39:55 preflight check successfully complete.
2024/09/13 01:39:55 generating pre-sign message.
2024/09/13 01:39:55 pre-sign world generated and serialized successfully.
2024/09/13 01:39:55 world has been signed.
2024/09/13 01:39:55 new signed world are packed.
2024/09/13 01:39:55 packed new signed world has been written to file.
2024/09/13 01:39:55
2024/09/13 01:39:55
2024/09/13 01:39:55 now c language output:
🖼 Screenshots
No response
The text was updated successfully, but these errors were encountered:
Workaround: This can be fixed by creating a identity.public with the controller's identity in /var/lib/zerotier-one or wherever you have mounted the folder.
As you found out, using a remote controller makes it difficult to create roots as ztnet needs access to the zerotier-one folder.
Your workarround would do, just remember if you change port others than 9993 you need to update the remote controller local.conf with the new port as well.
🐛 Describe the Bug
When a remote zerotier controller is setup in ZT Controller -> Controller -> Local ZeroTier URL/Zerotier Secret, setting up a new planet results in the error message
🔍 Steps to Reproduce
🌐 Browser
Chrome
🔧 Deployment Type
✨ Expected Behavior
ZTNet should use the existing entered identity to create the planet
📋 ZTNET Logs
🖼 Screenshots
No response
The text was updated successfully, but these errors were encountered: