Create Ziti Admin Console problem

TheLumberjack · January 31, 2023, 12:08am

Yes. That router input isn’t relevant yet. It’s just stating the controller isn’t able to be connected to.

Nick · January 31, 2023, 12:14am

Yes, I just run the code, and it will not stop, them I have to press ctrl + c to stop it.
The following is the output:

zhao2@zhao2:~$ “${ZITI_BIN_DIR-}/ziti-controller” run “${ZITI_HOME_OS_SPECIFIC}/${ZITI_EDGE_CONTROLLER_RAWNAME}.yaml”
[ 0.800] INFO ziti/ziti/controller.run: {arch=[amd64] build-date=[2023-01-04T20:13:07Z] version=[v0.27.2] go-version=[go1.19.4] revision=[7de87562b20d] nodeId=[zhao2] os=[linux]} starting ziti-controller
[ 0.801] INFO fabric/events.(*Dispatcher).eventLoop: event dispatcher: started
[ 0.801] INFO storage/boltz.(*migrationManager).Migrate.func1: fabric datastore is up to date at version 5
[ 0.837] INFO fabric/controller/network.(*Network).showOptions: network = {
“CycleSeconds”: 60,
“Smart”: {
“RerouteFraction”: 0.02,
“RerouteCap”: 4,
“MinCostDelta”: 15
},
“RouteTimeout”: 10000000000,
“CreateCircuitRetries”: 2,
“CtrlChanLatencyInterval”: 10000000000,
“PendingLinkTimeout”: 10000000000,
“MinRouterCost”: 10,
“RouterConnectChurnLimit”: 60000000000,
“InitialLinkLatency”: 65000000000,
“MetricsReportInterval”: 60000000000
}
[ 0.837] INFO fabric/controller.(*Controller).showOptions: ctrl = {
“OutQueueSize”: 4,
“MaxQueuedConnects”: 1,
“MaxOutstandingConnects”: 16,
“ConnectTimeout”: 1000000000,
“DelayRxStart”: false,
“WriteTimeout”: 0,
“NewListener”: null,
“AdvertiseAddress”: null
}
[ 1.493] INFO edge/controller/server.NewController: edge controller instance id: cldjhk82b0000noelmnmz2pv4
[ 1.493] INFO edge/controller/server.(*Controller).Initialize: initializing edge
[ 1.544] INFO storage/boltz.(*migrationManager).Migrate.func1: edge datastore is up to date at version 29
[ 1.582] INFO edge/controller/internal/policy.NewSessionEnforcer: {sessionTimeout=[30m0s] frequency=[5s]} session enforcer configured
[ 1.582] INFO edge/controller/server.(*Controller).Run: starting edge
[ 1.582] INFO fabric/metrics.GoroutinesPoolMetricsConfigF.func1.1: {idleTime=[10s] poolType=[pool.listener.ctrl] minWorkers=[1] maxQueueSize=[1] maxWorkers=[16]} starting goroutine pool
[ 1.583] INFO channel/v2.(*UnderlayDispatcher).Run: started
[ 1.588] INFO fabric/controller/network.(*Network).Run: started
[ 1.591] INFO edge/controller/server.(*Controller).checkEdgeInitialized: edge initialized
[ 1.714] INFO xweb/v2.(*Server).Start: starting ApiConfig to listen and serve tls on 0.0.0.0:1280 for server client-management with APIs: [edge-management edge-client fabric]
^C[ 43.040] INFO ziti/ziti/controller.waitForShutdown: shutting down ziti-controller
[ 43.040] INFO edge/controller/server.(*Controller).Shutdown: edge controller: shutting down…
[ 43.040] ERROR agent.(*handler).listen: {error=[accept unix /tmp/gops-agent.12516.sock: use of closed network connection]} error accepting gops connection, closing gops listener
[ 43.040] ERROR agent.(*handler).listen.func1: {error=[close unix /tmp/gops-agent.12516.sock: use of closed network connection]} error closing gops listener
[ 43.040] INFO edge/controller/server.(*Controller).Shutdown: edge controller: stopped
[ 43.040] INFO edge/controller/server.(*Controller).Shutdown: fabric controller: shutting down…
[ 43.040] INFO transport/v2/tls.(*acceptor).acceptLoop [classic/tls:0.0.0.0:6262]: {err=[accept tcp [::]:6262: use of closed network connection]} listener closed, exiting
[ 43.040] INFO transport/v2/tls.(*acceptor).acceptLoop [classic/tls:0.0.0.0:6262]: exited
[ 43.040] ERROR channel/v2.(*UnderlayDispatcher).Run: {error=[closed]} error accepting connection
[ 43.040] WARNING channel/v2.(*UnderlayDispatcher).Run: exited
[ 43.040] INFO fabric/events.(*Dispatcher).eventLoop: event dispatcher: stopped
[ 43.040] INFO fabric/controller/network.(*Network).Run: exited
zhao2@zhao2:~$

TheLumberjack · January 31, 2023, 12:19am

That’s really strange then… That tells me everything was setup properly and it’s running correctly. I’ve not seen the expressInstall fail like this yet.

Will you, delete the .ziti folder in the users home directory, close the shell (it’s important to close the shell), open a new shell, run the expressInstall and report what happens? It should go through the full, clean, expressInstall again. After it’s complete, run the startController function and see if it succeeds.

Nick · January 31, 2023, 11:33pm

Hi:

It still shows same problem, which is:

zhao@zhao:~$ zitiLogin
The connection to the server zhao:1280 was refused - did you specify the right host or port?
[2]+ Done “${ZITI_BIN_DIR-}/ziti-controller” run “${ZITI_HOME_OS_SPECIFIC}/${ZITI_EDGE_CONTROLLER_RAWNAME}.yaml” &> “${log_file}”

I have checked some possible problems:

I use ufw to open basically all ports:

root@zhao:~# ufw status
Status: active

To Action From

1:65535/tcp ALLOW Anywhere
1:65535/udp ALLOW Anywhere
1:65535/tcp (v6) ALLOW Anywhere (v6)
1:65535/udp (v6) ALLOW Anywhere (v6)

root@zhao:~#

I also checked /etc/hosts, and it’s content is:

127.0.0.1 localhost
127.0.1.1 zhao

The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

I also reinstalled the desktop’s OS to Ubuntu 20.04.5 LTS, and reinstall openZITI.

Is there any idea to solve this?

Nick · February 1, 2023, 12:09am

Hi:

I just got a little progress.

I changed a desktop and it works for “zitiLogin”, the current desktop’s OS is Debian GNU/Linux 11 bullseye (x86-64), and the current desktop is a new machine purchased within three years.

The desktop I used yesterday is very old, which is at least 10 years old with second gen Intel Core CPU.

However, I just wondering, is OpenZiti installation and using related to hardware AND the different Linux distributions (for example Ubuntu and Debian )?

If you want to know, I can share all the hardware configuration with you.

Best regards

TheLumberjack · February 1, 2023, 12:17am

Hi @Nick. Glad to see you have a little progress. We only officially support operating systems which are still receiving security updates. The age of the computer shouldn’t be the problem, but the OS on it might be.

I just wrote up a bunch of steps for another user. They might be helpful for you. They were having issues with RedHat working.

Could you take a look at the video I recorded and the steps as I perform them and maybe see how that works for you?

Find that post, video, and steps here: Admin Console not connecting to Edge Controller - #41 by TheLumberjack

Nick · February 1, 2023, 12:18am

Thank you very much sir.

Nick · February 1, 2023, 12:39am

Another problem:

when I run following code:

klabzhao@klabzhao:~$ “${ZITI_BIN_DIR-}/ziti” edge tutorial first-service

$ ziti edge login --ignore-config
Enter controller host[:port] (default localhost:1280):
Untrusted certificate authority retrieved from server
Verified that server supplied certificates are trusted by server
Server supplied 7 certificates
Trust server provided certificate authority [Y/N]: Y
Server certificate chain written to /home/klabzhao/.ziti/quickstart/klabzhao/certs/localhost
Enter username: klabzhao
Enter password:
error: unable to authenticate to https://localhost:1280/edge/management/v1. Status code: 401 Unauthorized, Server returned: {
“error”: {
“code”: “INVALID_AUTH”,
“message”: “The authentication request failed”,
“requestId”: “0pQKdN-bE”
},
“meta”: {
“apiEnrollmentVersion”: “0.0.1”,
“apiVersion”: “0.0.1”
}
}
operation failed with err: exit status 1. Retry [Y/N] (default Y):

I am sure the password is correct.

Any idea ?

TheLumberjack · February 1, 2023, 12:44am

If you followed the instructions from the other post, your password would be “myziti”, right? It sure looks like the password is incorrect.

I would start by trying to specify the user and password on the command line. for example:

ziti edge login localhost:1280 -u admin -p myziti -y

Nick · February 1, 2023, 6:16pm

Hi:

Thank you very much.
Now, I have finished the “local-no docker” express installation, And I am installing the ziti admin console with GUI.
However, I am facing following problem and error message:
In short, now the ziti-console.service cannot be activated by command “sudo systemctl status ziti-console --lines=0 --no-pager”.
AND in brower, no matter I input https://localhost:8443/ or https://klabzhao:8443/, it shows “We can’t connect to the server at ${ziti_edge_controller_hostname}.”
Now I am using “Debian GNU/Linux 11 bullseye (x86-64)”
Could please share some idea to solve this?
Thank you

klabzhao@klabzhao:~$ cd “${ZITI_HOME}/ziti-console”
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ npm install
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘io.netfoundry.zac@2.5.7’,
npm WARN EBADENGINE required: { node: ‘>=18.13.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@apidevtools/json-schema-ref-parser@10.0.1’,
npm WARN EBADENGINE required: { node: ‘>= 17’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘helmet@6.0.1’,
npm WARN EBADENGINE required: { node: ‘>=14.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘npm@9.4.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/arborist@6.2.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/config@6.1.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/disparity-colors@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/fs@3.1.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/git@4.0.3’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/installed-package-contents@2.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/map-workspaces@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/metavuln-calculator@5.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/node-gyp@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/package-json@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/promise-spawn@6.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/query@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@npmcli/run-script@6.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘abbrev@2.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘are-we-there-yet@4.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘bin-links@4.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘cacache@17.0.3’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘cmd-shim@6.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘gauge@5.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘hosted-git-info@6.1.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘ignore-walk@6.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘init-package-json@4.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘json-parse-even-better-errors@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘libnpmaccess@7.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘libnpmdiff@5.0.8’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘libnpmexec@5.0.8’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘libnpmfund@4.0.8’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘libnpmhook@9.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘libnpmorg@5.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘libnpmpack@5.0.8’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘libnpmpublish@7.0.6’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘libnpmsearch@6.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘libnpmteam@5.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘libnpmversion@4.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘make-fetch-happen@11.0.2’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘minipass-fetch@3.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘nopt@7.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘normalize-package-data@5.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘npm-audit-report@4.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘npm-bundled@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘npm-install-checks@6.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘npm-normalize-package-bin@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘npm-package-arg@10.1.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘npm-packlist@7.0.4’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘npm-pick-manifest@8.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘npm-profile@7.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘npm-registry-fetch@14.0.3’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘npmlog@7.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘pacote@15.0.7’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘parse-conflict-json@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘proc-log@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘read-cmd-shim@4.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘read-package-json@6.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘read-package-json-fast@3.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘ssri@10.0.1’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘treeverse@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘unique-filename@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘unique-slug@4.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘validate-npm-package-name@5.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘which@3.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘write-file-atomic@5.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }
npm WARN EBADENGINE }

removed 2 packages, and audited 373 packages in 847ms

22 packages are looking for funding
run npm fund for details

found 0 vulnerabilities
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ ln -s “${ZITI_PKI}/${ZITI_EDGE_CONTROLLER_HOSTNAME}-intermediate/certs/${ZITI_EDGE_CONTROLLER_HOSTNAME}-server.chain.pem” “${ZITI_HOME}/ziti-console/server.chain.pem”
ln: failed to create symbolic link ‘/home/klabzhao/.ziti/quickstart/klabzhao/ziti-console/server.chain.pem’: File exists
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ ln -s “${ZITI_PKI}/${ZITI_EDGE_CONTROLLER_HOSTNAME}-intermediate/keys/${ZITI_EDGE_CONTROLLER_HOSTNAME}-server.key” “${ZITI_HOME}/ziti-console/server.key”
ln: failed to create symbolic link ‘/home/klabzhao/.ziti/quickstart/klabzhao/ziti-console/server.key’: File exists
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ createZacSystemdFile
sudo cp “${ZITI_HOME}/ziti-console.service” /etc/systemd/system
sudo systemctl daemon-reload
sudo systemctl enable --now ziti-console
This will overwrite the existing file, continue (y/N)? y
ziti-console systemd file written to: /home/klabzhao/.ziti/quickstart/klabzhao/ziti-console.service
[sudo] password for klabzhao:
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ node “${ZITI_HOME}/ziti-console/server.js”
file:///home/klabzhao/.ziti/quickstart/klabzhao/ziti-console/server.js:36
ziti = await loadModule(‘@openziti/ziti-sdk-nodejs’)
^^^^^

SyntaxError: Unexpected reserved word
at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)
at async link (internal/modules/esm/module_job.js:42:21)
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ sudo systemctl status ziti-console --lines=0 --no-pager
● ziti-console.service - Ziti-Console
Loaded: loaded (/etc/systemd/system/ziti-console.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2023-02-01 10:06:37 PST; 1s ago
Process: 2391627 ExecStart=/usr/bin/node /home/klabzhao/.ziti/quickstart/klabzhao/ziti-console/server.js (code=exited, status=1/FAILURE)
Main PID: 2391627 (code=exited, status=1/FAILURE)
CPU: 60ms
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ sudo systemctl status ziti-console --lines=0 --no-pager
● ziti-console.service - Ziti-Console
Loaded: loaded (/etc/systemd/system/ziti-console.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2023-02-01 10:06:49 PST; 1s ago
Process: 2391686 ExecStart=/usr/bin/node /home/klabzhao/.ziti/quickstart/klabzhao/ziti-console/server.js (code=exited, status=1/FAILURE)
Main PID: 2391686 (code=exited, status=1/FAILURE)
CPU: 62ms
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ node “${ZITI_HOME}/ziti-console/server.js”
Initializing TLS
TLS initialized on port: 8443
Ziti Server running on port 1408
file:///home/klabzhao/.ziti/quickstart/klabzhao/ziti-console/server.js:36
ziti = await loadModule(‘@openziti/ziti-sdk-nodejs’)
^^^^^

SyntaxError: Unexpected reserved word
at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)
at async link (internal/modules/esm/module_job.js:42:21)
bash: Initializing: command not found
bash: TLS: command not found
bash: Ziti: command not found

TheLumberjack · February 1, 2023, 6:25pm

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘write-file-atomic@5.0.0’,
npm WARN EBADENGINE required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }

make sure your node is 16+ and npm is 8+ and i bet it’ll work. you can run

npm version

to see what you have (it looks like node 12 and npm 7)

Nick · February 1, 2023, 6:28pm

klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ npm version
{
‘io.netfoundry.zac’: ‘2.5.7’,
npm: ‘7.5.2’,
node: ‘12.22.12’,
v8: ‘7.8.279.23-node.57’,
uv: ‘1.40.0’,
zlib: ‘1.2.11’,
brotli: ‘1.0.9’,
ares: ‘1.17.1’,
modules: ‘72’,
nghttp2: ‘1.43.0’,
napi: ‘8’,
llhttp: ‘2.1.6’,
http_parser: ‘2.9.4’,
openssl: ‘1.1.1n’,
cldr: ‘37.0’,
icu: ‘67.1’,
tz: ‘2019c’,
unicode: ‘13.0’
}

TheLumberjack · February 1, 2023, 6:33pm

As stated, your node is too old. It states that you need 14+ for node. Please upgrade your node environment. I’d recommend 16+

TheLumberjack · February 1, 2023, 6:35pm

you need node to run one of these versions:

required: { node: ‘^14.17.0 || ^16.13.0 || >=18.0.0’ }`

but the current node is v12:

current: { node: ‘v12.22.12’, npm: ‘7.5.2’ }

Nick · February 1, 2023, 6:50pm

Hi:

I opened another terminal to install newest version of node.
Then, when I go back to the terminal I run the ziti-consle to run npm install again, it shows:
should I restart everything ?

klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ npm install
node:internal/modules/cjs/loader:1063
throw err;
^

Error: Cannot find module ‘semver’
Require stack:

/usr/share/nodejs/npm/lib/utils/unsupported.js
/usr/share/nodejs/npm/lib/cli.js
/usr/share/nodejs/npm/bin/npm-cli.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1060:15)
at Module._load (node:internal/modules/cjs/loader:905:27)
at Module.require (node:internal/modules/cjs/loader:1127:19)
at require (node:internal/modules/helpers:112:18)
at Object. (/usr/share/nodejs/npm/lib/utils/unsupported.js:1:16)
at Module._compile (node:internal/modules/cjs/loader:1246:14)
at Module._extensions…js (node:internal/modules/cjs/loader:1300:10)
at Module.load (node:internal/modules/cjs/loader:1103:32)
at Module._load (node:internal/modules/cjs/loader:942:12)
at Module.require (node:internal/modules/cjs/loader:1127:19) {
code: ‘MODULE_NOT_FOUND’,
requireStack: [
‘/usr/share/nodejs/npm/lib/utils/unsupported.js’,
‘/usr/share/nodejs/npm/lib/cli.js’,
‘/usr/share/nodejs/npm/bin/npm-cli.js’
]
}

Node.js v19.5.0
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ npm version
node:internal/modules/cjs/loader:1063
throw err;
^

Error: Cannot find module ‘semver’
Require stack:

/usr/share/nodejs/npm/lib/utils/unsupported.js
/usr/share/nodejs/npm/lib/cli.js
/usr/share/nodejs/npm/bin/npm-cli.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1060:15)
at Module._load (node:internal/modules/cjs/loader:905:27)
at Module.require (node:internal/modules/cjs/loader:1127:19)
at require (node:internal/modules/helpers:112:18)
at Object. (/usr/share/nodejs/npm/lib/utils/unsupported.js:1:16)
at Module._compile (node:internal/modules/cjs/loader:1246:14)
at Module._extensions…js (node:internal/modules/cjs/loader:1300:10)
at Module.load (node:internal/modules/cjs/loader:1103:32)
at Module._load (node:internal/modules/cjs/loader:942:12)
at Module.require (node:internal/modules/cjs/loader:1127:19) {
code: ‘MODULE_NOT_FOUND’,
requireStack: [
‘/usr/share/nodejs/npm/lib/utils/unsupported.js’,
‘/usr/share/nodejs/npm/lib/cli.js’,
‘/usr/share/nodejs/npm/bin/npm-cli.js’
]
}

Node.js v19.5.0

TheLumberjack · February 1, 2023, 6:54pm

@jeremy.tellier – does ZAC work with node 19? I feel like maybe node 19 made a change?

Nick · February 1, 2023, 7:01pm

Hi:

I have changed it to node 18.13.
In another terminal it shows:

klabzhao@klabzhao:~$ npm version
{
npm: ‘8.19.3’,
node: ‘18.13.0’,
v8: ‘10.2.154.23-node.21’,
uv: ‘1.44.2’,
zlib: ‘1.2.13’,
brotli: ‘1.0.9’,
ares: ‘1.18.1’,
modules: ‘108’,
nghttp2: ‘1.51.0’,
napi: ‘8’,
llhttp: ‘6.0.10’,
uvwasi: ‘0.0.13’,
openssl: ‘3.0.7+quic’,
cldr: ‘42.0’,
icu: ‘72.1’,
tz: ‘2022f’,
unicode: ‘15.0’,
ngtcp2: ‘0.8.1’,
nghttp3: ‘0.7.0’
}

However, in the terminal I run ziti, it shows:

klabzhao@klabzhao:~$ npm install
node:internal/modules/cjs/loader:1042
throw err;
^

Error: Cannot find module ‘semver’
Require stack:

/usr/share/nodejs/npm/lib/utils/unsupported.js
/usr/share/nodejs/npm/lib/cli.js
/usr/share/nodejs/npm/bin/npm-cli.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)
at Module._load (node:internal/modules/cjs/loader:885:27)
at Module.require (node:internal/modules/cjs/loader:1105:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object. (/usr/share/nodejs/npm/lib/utils/unsupported.js:1:16)
at Module._compile (node:internal/modules/cjs/loader:1218:14)
at Module._extensions…js (node:internal/modules/cjs/loader:1272:10)
at Module.load (node:internal/modules/cjs/loader:1081:32)
at Module._load (node:internal/modules/cjs/loader:922:12)
at Module.require (node:internal/modules/cjs/loader:1105:19) {
code: ‘MODULE_NOT_FOUND’,
requireStack: [
‘/usr/share/nodejs/npm/lib/utils/unsupported.js’,
‘/usr/share/nodejs/npm/lib/cli.js’,
‘/usr/share/nodejs/npm/bin/npm-cli.js’
]
}

Node.js v18.13.0
klabzhao@klabzhao:~$ npm version
node:internal/modules/cjs/loader:1042
throw err;
^

Error: Cannot find module ‘semver’
Require stack:

/usr/share/nodejs/npm/lib/utils/unsupported.js
/usr/share/nodejs/npm/lib/cli.js
/usr/share/nodejs/npm/bin/npm-cli.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)
at Module._load (node:internal/modules/cjs/loader:885:27)
at Module.require (node:internal/modules/cjs/loader:1105:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object. (/usr/share/nodejs/npm/lib/utils/unsupported.js:1:16)
at Module._compile (node:internal/modules/cjs/loader:1218:14)
at Module._extensions…js (node:internal/modules/cjs/loader:1272:10)
at Module.load (node:internal/modules/cjs/loader:1081:32)
at Module._load (node:internal/modules/cjs/loader:922:12)
at Module.require (node:internal/modules/cjs/loader:1105:19) {
code: ‘MODULE_NOT_FOUND’,
requireStack: [
‘/usr/share/nodejs/npm/lib/utils/unsupported.js’,
‘/usr/share/nodejs/npm/lib/cli.js’,
‘/usr/share/nodejs/npm/bin/npm-cli.js’
]
}

Node.js v18.13.0

Nick · February 1, 2023, 7:04pm

I just did this:

klabzhao@klabzhao:~$ node -v
v19.5.0
klabzhao@klabzhao:~$ sudo npm cache clean -f
sudo npm install -g n
sudo n stable
npm WARN using --force Recommended protections disabled.

changed 1 package in 279ms
copying : node/18.13.0
installed : v18.13.0 (with npm 8.19.3)
klabzhao@klabzhao:~$ npm version
{
npm: ‘8.19.3’,
node: ‘18.13.0’,
v8: ‘10.2.154.23-node.21’,
uv: ‘1.44.2’,
zlib: ‘1.2.13’,
brotli: ‘1.0.9’,
ares: ‘1.18.1’,
modules: ‘108’,
nghttp2: ‘1.51.0’,
napi: ‘8’,
llhttp: ‘6.0.10’,
uvwasi: ‘0.0.13’,
openssl: ‘3.0.7+quic’,
cldr: ‘42.0’,
icu: ‘72.1’,
tz: ‘2022f’,
unicode: ‘15.0’,
ngtcp2: ‘0.8.1’,
nghttp3: ‘0.7.0’
}
klabzhao@klabzhao:~$

TheLumberjack · February 1, 2023, 7:04pm

ooh. you need to be in the ziti-console checkout before running npm install…

cd $HOME/.ziti/quickstart/$(hostname -s)/ziti-console

then run npm install. i think you’re skipping some steps

Nick · February 1, 2023, 7:07pm

Some steps?
What steps I need to re-do?
If I just run “$HOME/.ziti/quickstart/klabzhao/ziti-console”, it still shows:

klabzhao@klabzhao:~$ cd
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ npm version
node:internal/modules/cjs/loader:1042
throw err;
^

Error: Cannot find module ‘semver’
Require stack:

/usr/share/nodejs/npm/lib/utils/unsupported.js
/usr/share/nodejs/npm/lib/cli.js
/usr/share/nodejs/npm/bin/npm-cli.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)
at Module._load (node:internal/modules/cjs/loader:885:27)
at Module.require (node:internal/modules/cjs/loader:1105:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object. (/usr/share/nodejs/npm/lib/utils/unsupported.js:1:16)
at Module._compile (node:internal/modules/cjs/loader:1218:14)
at Module._extensions…js (node:internal/modules/cjs/loader:1272:10)
at Module.load (node:internal/modules/cjs/loader:1081:32)
at Module._load (node:internal/modules/cjs/loader:922:12)
at Module.require (node:internal/modules/cjs/loader:1105:19) {
code: ‘MODULE_NOT_FOUND’,
requireStack: [
‘/usr/share/nodejs/npm/lib/utils/unsupported.js’,
‘/usr/share/nodejs/npm/lib/cli.js’,
‘/usr/share/nodejs/npm/bin/npm-cli.js’
]
}

Node.js v18.13.0
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$ npm install
node:internal/modules/cjs/loader:1042
throw err;
^

Error: Cannot find module ‘semver’
Require stack:

/usr/share/nodejs/npm/lib/utils/unsupported.js
/usr/share/nodejs/npm/lib/cli.js
/usr/share/nodejs/npm/bin/npm-cli.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)
at Module._load (node:internal/modules/cjs/loader:885:27)
at Module.require (node:internal/modules/cjs/loader:1105:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object. (/usr/share/nodejs/npm/lib/utils/unsupported.js:1:16)
at Module._compile (node:internal/modules/cjs/loader:1218:14)
at Module._extensions…js (node:internal/modules/cjs/loader:1272:10)
at Module.load (node:internal/modules/cjs/loader:1081:32)
at Module._load (node:internal/modules/cjs/loader:922:12)
at Module.require (node:internal/modules/cjs/loader:1105:19) {
code: ‘MODULE_NOT_FOUND’,
requireStack: [
‘/usr/share/nodejs/npm/lib/utils/unsupported.js’,
‘/usr/share/nodejs/npm/lib/cli.js’,
‘/usr/share/nodejs/npm/bin/npm-cli.js’
]
}

Node.js v18.13.0
klabzhao@klabzhao:~/.ziti/quickstart/klabzhao/ziti-console$