After NNX my original node I update system and now can not connect

My system setup is-

Use Installed ASL packages :

Package Version
============================== ==============================
allmon3 1.6.0-3.deb12
asl3 3.9-1.deb12
asl3-asterisk 2:22.4.1+asl3-3.5.5-1.deb12
asl3-asterisk-config 2:22.4.1+asl3-3.5.5-1.deb12
asl3-asterisk-modules 2:22.4.1+asl3-3.5.5-1.deb12
asl3-menu 1.14-1.deb12
asl3-pi-appliance 1.10.0-1.deb12
asl3-tts 1.0.1-1.deb12
asl3-update-nodelist 1.5.1-1.deb12
cockpit 287.1-0+deb12u3
cockpit-bridge 287.1-0+deb12u3
cockpit-networkmanager 287.1-0+deb12u3
cockpit-packagekit 287.1-0+deb12u3
cockpit-sosreport 287.1-0+deb12u3
cockpit-storaged 287.1-0+deb12u3
cockpit-system 287.1-0+deb12u3
cockpit-wifimanager 1.1.1-1.deb12
cockpit-ws 287.1-0+deb12u3
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-8.asl.deb12
dahdi-linux 1:3.4.0-8.asl.deb12 to obtain this information from the console or SSH

I am having issues after NNX 66733 to 667330. I have updated the rpt.conf, extensions.conf, and iax.conf per the wiki direction "NNX on your AllStar Node"

I am not able to connect using my private node to my new NNX node 667330. The rejection says "can not connect". This was able to do it prior to NNX changes. The new node number is showing registered;

Host Username Perceived Refresh State
52 20 63 146 443 667330 73 156 166 63 4569 179 Registered

asl-node-lookup 667330

TXT (667330
NN=667330
RT=2025-09-21 23:24:57
RB=0
IP=73.156.166.63
PIP=0
PT=4569
RH=aws-east1a-register0

The logs-

[2025-09-21 19:16:30.817] WARNING[126424][C-00000022] app_rpt.c: Cannot find specified system node 66733
[2025-09-21 19:19:49.869] WARNING[138918][C-00000026] app_rpt.c: Cannot find specified system node 66733
[2025-09-21 19:24:56.480] WARNING[158037][C-0000002a] app_rpt.c: Cannot find specified system node 66733

ifconfig - 73.156.166.63 2601:6c4:c181:6c20::6914

I do not know what to do next.

Thank you in advance,

Drew KN4YDL

All should be better now.

And, so you know, have a look at ASL3 Manual : Issues with connections to "new" NNX Nodes

Hi, I appear to have a similar issue. I have waited the 24 hrs for the servers to update as per the instructions in the link WA3WCO posted above, but when trying to connect my 668412 to 688411 it appears to connect to 66841 (no extension) but of course this is not valid. Below is the output from /var/log/asterisk/messages.log - any suggestions on what I should try next? Thanks.

I have removed the leftover pre-NNX DNS records for node 66841.

... AND I think I know why the cleanup code didn't do what it was supposed to do. Getting the backend processing issue resolved **IS** on my list.

Thankyou. It is all working now. Appreciate your assistance.