Closed gerrymanley closed 3 years ago
Ztncui is compiled for x86_64, not ARM.
Sorry, I didn't notice you were running it manually... have you tried generating the cert as per the README at https://github.com/key-networks/ztncui ?
It should be built/run with nodejs v8.
Thanks, I'll do a new install on an x86_64 with nodejs v8 and see how it goes.
@gerrymanley have you been able to start ztncui on RPi3?
Sorry Have no time at present, just started new employment, getting home very late
On Thu, 12 Nov 2020, 01:24 Jarusss, notifications@github.com wrote:
@gerrymanley https://github.com/gerrymanley have you been able to start ztncui on RPi3?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/key-networks/ztncui/issues/44#issuecomment-725740483, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADKH4QBYE7FN6WD6SBCOW4TSPMTKTANCNFSM4TCIDVMA .
@gerrymanley, @key-networks I was able to install it on RPi3 (with errors do not know why, but it is working:) ). I was able to add members from local network and from Internet, so I think everything works fine! :)
@key-networks I have a stupid question - on ZT page in pricing I can see that there is a limit of 50nodes. As I understand this limit is only when I use ZT by itself, when I build my own server this limit does not exist?
The Node limits set by Zerotier are only compliant when you use their online services. As long as you are creating your own ZT networks and registering your nodes to the same network(s) - no charge from ZT as long these networks are not used commercially
From ZT's website: ZeroTier’s software kit is licensed under the ZeroTier BSL, which allows source code access and free use for all with the exception of hosting a network controller for commercial purposes or embedding the ZeroTier source code in a commercial application. You can self-host ZeroTier controllers and nodes for free if you use it for non-commercial purposes.
On Thu, Nov 12, 2020 at 12:59 PM Jarusss notifications@github.com wrote:
@gerrymanley https://github.com/gerrymanley, @key-networks https://github.com/key-networks I was able to install it on RPi3 (with errors do not know why, but it is working:) ). I was able to add members from local network and from Internet, so I think everything works fine! :)
@key-networks https://github.com/key-networks I have a stupid question
- on ZT page in pricing I can see that there is a limit of 50nodes. As I understand this limit is only when I use ZT by itself, when I build my own server this limit does not exist?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/key-networks/ztncui/issues/44#issuecomment-726034370, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADKH4QEXWXY6TSWZOQEJZM3SPPEZBANCNFSM4TCIDVMA .
-- Best regards
Gerry Manley
Contact details: Kyrkbyn 6 14565 Norsborg gsm: +46 709980171 http://www.linkedin.com/pub/gerry-manley/4/835/46b
Hi, I've been using the controller services at zerotier.com for awhile and have just started with an ztncui installation on a rasp pi 3.
I only get as far as npm start and get this:
sudo npm start
fs.js:114 throw err; ^
Error: ENOENT: no such file or directory, open 'etc/tls/fullchain.pem' at Object.openSync (fs.js:443:3) at Object.readFileSync (fs.js:343:35) at Object. (/home/pi/ztncui/src/bin/www:14:12)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
at startup (internal/bootstrap/node.js:283:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ztncui@0.5.8 start:
node ./bin/www
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the ztncui@0.5.8 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2020-10-28T12_14_38_456Z-debug.log
I check the log file and get this:
0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'start' ] 2 info using npm@6.14.8 3 info using node@v10.21.0 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle ztncui@0.5.8~prestart: ztncui@0.5.8 6 info lifecycle ztncui@0.5.8~start: ztncui@0.5.8 7 verbose lifecycle ztncui@0.5.8~start: unsafe-perm in lifecycle true 8 verbose lifecycle ztncui@0.5.8~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/ztncui/src/node_modules/.bin:/usr/loc$ 9 verbose lifecycle ztncui@0.5.8~start: CWD: /home/pi/ztncui/src 10 silly lifecycle ztncui@0.5.8~start: Args: [ '-c', 'node ./bin/www' ] 11 silly lifecycle ztncui@0.5.8~start: Returned: code: 1 signal: null 12 info lifecycle ztncui@0.5.8~start: Failed to exec start script 13 verbose stack Error: ztncui@0.5.8 start: (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid ztncui@0.5.8
15 verbose cwd /home/pi/ztncui/src
16 verbose Linux 5.4.51-v7+
17 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "start"
18 verbose node v10.21.0
19 verbose npm v6.14.8
20 error code ELIFECYCLE
21 error errno 1
22 error ztncui@0.5.8 start:
node ./bin/www
13 verbose stack Exit status 1 13 verbose stack at EventEmitter.node ./bin/www
Just wondering if this has to do with me using the latest versions of npm 6.14.8 & nodejs v10.21.0