e-server-hcmc.jwt: No such file or directory
nyck33@nyck-old-lenovo:~/c2c/hogugu-cursorai-memory$ ziti edge enroll --jwt /home/nyck33/c2c/openziti/secrets/node-server-hcmc.jwt
INFO generating 4096 bit RSA key
INFO enrolled successfully. identity file written to: /home/nyck33/c2c/openziti/secrets/node-server-hcmc.json
nyck33@nyck-old-lenovo:~/c2c/hogugu-cursorai-memory$ ls /home/nyck33/c2c/openziti/secrets/
node-server-hcmc.json
node-server-hcmc.jwt:Zone.Identifier
node-server-lenovo-old.jwt
node-server-lenovo-old.jwt:Zone.Identifier
node-server-old-lenovo.json
nyck33@nyck-old-lenovo:~/c2c/hogugu-cursorai-memory$ npm run dev
> hogugu-web-booking@2.1.1 dev
> ts-node -P tsconfig.server.json server.ts
info - Loaded env from /home/nyck33/c2c/hogugu-cursorai-memory/.env
warn - You have enabled experimental feature (scrollRestoration) in next.config.js.
warn - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
event - compiled client and server successfully in 18.6s (2329 modules)
Starting Ziti initialization...
(353665)[ 0.000] INFO ziti-sdk:utils.c:198 ziti_log_set_level() set log level: root=6/TRACE
(353665)[ 0.000] INFO ziti-sdk:utils.c:167 ziti_log_init() Ziti C SDK version 1.3.5 @gcd0b42b(HEAD) starting at (2025-01-22T14:32:02.730)
(353665)[ 0.105] INFO ziti-sdk:ziti.c:505 ziti_start_internal() ztx[0] enabling Ziti Context
(353665)[ 0.105] INFO ziti-sdk:ziti.c:522 ziti_start_internal() ztx[0] using tlsuv[v0.33.2/OpenSSL 3.0.15+quic 3 Sep 2024]
(353665)[ 0.105] INFO ziti-sdk:ziti_ctrl.c:632 ziti_ctrl_init() ctrl[(null):] using https://11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443/edge/client/v1
(353665)[ 0.105] DEBUG ziti-sdk:ziti_ctrl.c:646 ziti_ctrl_init() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] ziti controller client initialized
(353665)[ 0.105] VERBOSE ziti-sdk:ziti_ctrl.c:152 start_request() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] starting GET[/version]
(353665)[ 0.105] INFO ziti-sdk:ziti.c:600 ztx_init_controller() ztx[0] Loading ziti context with controller[https://11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443/edge/client/v1]
(353665)[ 0.105] DEBUG ziti-sdk:ziti.c:531 ziti_start_internal() ztx[0] using metrics interval: 6
(353665)[ 0.105] DEBUG ziti-sdk:ziti.c:218 ziti_set_unauthenticated() ztx[0] setting auth_state[0] to 0
(353665)[ 0.105] DEBUG ziti-sdk:ziti_ctrl.c:386 ziti_ctrl_clear_api_session() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] clearing api session token for ziti_controller
(353665)[ 0.105] DEBUG ziti-sdk:ziti_ctrl.c:1071 ctrl_paging_req() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] starting paging request GET[/external-jwt-signers]
(353665)[ 0.105] VERBOSE ziti-sdk:ziti_ctrl.c:1076 ctrl_paging_req() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] requesting /external-jwt-signers?limit=25&offset=0
(353665)[ 0.105] VERBOSE ziti-sdk:ziti_ctrl.c:152 start_request() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] starting GET[/external-jwt-signers?limit=25&offset=0]
Segmentation fault (core dumped)
nyck33@nyck-old-lenovo:~/c2c/hogugu-cursorai-memory$
that took 10 minutes and now it's registered? can you speed that up a bit?
This is not clear enough for me to understand what you are doing or what you think went wrong.
a
this time it registered and cannot detect it's wsl2.
this time it registered and cannot detect it's wsl2.
so I switched out the identity to node-server-hcmc for the service and policy:
but keeping getting seg faults
nyck33@nyck-old-lenovo:~/c2c/hogugu-cursorai-memory$ npm run dev
> hogugu-web-booking@2.1.1 dev
> ts-node -P tsconfig.server.json server.ts
Step 1: Preparing Next.js
Step 2: Initializing Ziti
(360835)[ 0.000] INFO ziti-sdk:utils.c:198 ziti_log_set_level() set log level: root=6/TRACE
(360835)[ 0.000] INFO ziti-sdk:utils.c:167 ziti_log_init() Ziti C SDK version 1.3.5 @gcd0b42b(HEAD) starting at (2025-01-22T14:58:06.083)
Step 3: Waiting for Next.js
info - Loaded env from /home/nyck33/c2c/hogugu-cursorai-memory/.env
(360835)[ 2.618] INFO ziti-sdk:ziti.c:505 ziti_start_internal() ztx[0] enabling Ziti Context
(360835)[ 2.618] INFO ziti-sdk:ziti.c:522 ziti_start_internal() ztx[0] using tlsuv[v0.33.2/OpenSSL 3.0.15+quic 3 Sep 2024]
(360835)[ 2.618] INFO ziti-sdk:ziti_ctrl.c:632 ziti_ctrl_init() ctrl[(null):] using https://11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443/edge/client/v1
(360835)[ 2.618] DEBUG ziti-sdk:ziti_ctrl.c:646 ziti_ctrl_init() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] ziti controller client initialized
(360835)[ 2.618] VERBOSE ziti-sdk:ziti_ctrl.c:152 start_request() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] starting GET[/version]
(360835)[ 2.618] INFO ziti-sdk:ziti.c:600 ztx_init_controller() ztx[0] Loading ziti context with controller[https://11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443/edge/client/v1]
(360835)[ 2.618] DEBUG ziti-sdk:ziti.c:531 ziti_start_internal() ztx[0] using metrics interval: 6
(360835)[ 2.618] DEBUG ziti-sdk:ziti.c:218 ziti_set_unauthenticated() ztx[0] setting auth_state[0] to 0
(360835)[ 2.618] DEBUG ziti-sdk:ziti_ctrl.c:386 ziti_ctrl_clear_api_session() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] clearing api session token for ziti_controller
(360835)[ 2.618] DEBUG ziti-sdk:ziti_ctrl.c:1071 ctrl_paging_req() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] starting paging request GET[/external-jwt-signers]
(360835)[ 2.618] VERBOSE ziti-sdk:ziti_ctrl.c:1076 ctrl_paging_req() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] requesting /external-jwt-signers?limit=25&offset=0
(360835)[ 2.618] VERBOSE ziti-sdk:ziti_ctrl.c:152 start_request() ctrl[11c1453a-8f7c-4d6e-9fc3-1a9c7c251c17.production.netfoundry.io:443] starting GET[/external-jwt-signers?limit=25&offset=0]
warn - You have enabled experimental feature (scrollRestoration) in next.config.js.
warn - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
Segmentation fault (core dumped)
nyck33@nyck-old-lenovo:~/c2c/hogugu-cursorai-memory$
my code:
import express from 'express';
import next from 'next';
import { parse } from 'url';
import { config } from 'dotenv';
import ziti from '@openziti/ziti-sdk-nodejs';
import type { Request, Response } from 'express';
async function main() {
// Load environment variables first
const result = config();
if (result.error) {
console.error('Failed to load .env file:', result.error);
process.exit(1);
}
// Get Ziti config
const identityFile = process.env.ZITI_IDENTITY_FILE;
const serviceName = process.env.ZITI_SERVICE_NAME;
if (!identityFile || !serviceName) {
console.error('Missing required environment variables');
process.exit(1);
}
// Step 1: Initialize Next.js
console.log('Step 1: Preparing Next.js');
const dev = process.env.NODE_ENV !== 'production';
const nextApp = next({ dev });
const handle = nextApp.getRequestHandler();
// Step 2: Initialize Ziti
console.log('Step 2: Initializing Ziti');
ziti.init(identityFile);
// Step 3: Wait for Next.js
console.log('Step 3: Waiting for Next.js');
await nextApp.prepare();
console.log('Step 3: Next.js ready');
// Step 4: Create server
console.log('Step 4: Creating server');
const app = ziti.express(express, serviceName);
app.all('*', function(req: Request, res: Response) {
const parsedUrl = parse(req.url!, true);
handle(req, res, parsedUrl);
});
app.listen(0, function() {
console.log('> Ready on Ziti service:', serviceName);
});
}
main().catch(function(error) {
console.error('Failed to start server:', error);
process.exit(1);
});
for a next.js app that is server.ts in project root.
with the node-server
identity in place of node-server-hcmc
on my other computer, at least I could kind of get on the overlay although it was having issues.
Ok I think I understand better. You're using the node sdk, and it's seg faulting, now I understand. I'm not familiar enough with it sadly. I dunno if you can get a stack dump/crash dump from node, but that would be really helpful.