Netonix Forums

I have a new install of Ubuntu 20.04.2.0 LTS Desktop version. Installed nodejs and netonix-manager status shows active(running).
I cant open it in the browser https://localhost:3443 Nothing is listening on port 3443, Any ideas on what is missing?

Could be a couple things, what version of node is on your system?

Current version show 10.19.0 I have tried 8.16.0 and 14.16.1. All have the same issue

Try using version node 8.1.2 (it's easy to switch with nvm if you don't already use it)
Then completely uninstall the manager and try installing it again.

Let's see how that goes.

Still the same issue.

oot@gene-NUC8i7BEH:/home/gene# ss -ltn
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 5 127.0.0.1:631 0.0.0.0:*
LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:*
LISTEN 0 5 [::1]:631 [::]:*
LISTEN 0 511 *:80 *:*
root@gene-NUC8i7BEH:/home/gene# service netonix-manager status
● netonix-manager.service - LSB: Start daemon at boot time
Loaded: loaded (/etc/init.d/netonix-manager; generated)
Active: active (running) since Sun 2021-05-02 11:52:08 CDT; 30s ago
Docs: man:systemd-sysv-generator(8)
Process: 8314 ExecStart=/etc/init.d/netonix-manager start (code=exited, status=0/SUCCESS)
Tasks: 13 (limit: 38308)
Memory: 60.9M
CGroup: /system.slice/netonix-manager.service
├─8317 /usr/bin/nodejs bootloader.js
└─8960 nodejs app.js

May 02 11:52:08 gene-NUC8i7BEH systemd[1]: Starting LSB: Start daemon at boot time...
May 02 11:52:08 gene-NUC8i7BEH systemd[1]: Started LSB: Start daemon at boot time.
root@gene-NUC8i7BEH:/home/gene# node -v
v8.2.1
root@gene-NUC8i7BEH:/home/gene#

I still have not been able to get this working, what am I missing?

Could you PM me the crashlog?

It should be located at

Code: Select all

/opt/netonix-manager/crash.log


It's possible this might be the issue, try this:

In the file /etc/ssl/openssl.cnf changing last line
from:

Code: Select all

CipherString = DEFAULT@SECLEVEL=2


to

Code: Select all

CipherString = DEFAULT@SECLEVEL=1


CipherString line does not exist in the file.

I tried PM just stuck in outbox..

Here is the text from crash.log just keeps repeating

js-bson: Failed to load c++ bson extension, using pure JS version
_tls_common.js:135
c.context.setCert(cert);
^

Error: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small
at Object.createSecureContext (_tls_common.js:135:17)
at Server (_tls_wrap.js:873:27)
at new Server (https.js:62:14)
at Object.createServer (https.js:85:10)
at Object.<anonymous> (/opt/netonix-manager/app.js:920:11)
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)
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
js-bson: Failed to load c++ bson extension, using pure JS version
_tls_common.js:135
c.context.setCert(cert);
^

Error: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small
at Object.createSecureContext (_tls_common.js:135:17)
at Server (_tls_wrap.js:873:27)
at new Server (https.js:62:14)
at Object.createServer (https.js:85:10)
at Object.<anonymous> (/opt/netonix-manager/app.js:920:11)
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)
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
js-bson: Failed to load c++ bson extension, using pure JS version
_tls_common.js:135
c.context.setCert(cert);
^

OK i see the issue,

I'm going to have to do a bit more research to fix this issue but it is related to this version of Ubuntu.
I am able to run the manager on Ubuntu version 18.04.5 LTS if you can move back to that version, you should be OK.