Node is ONLINE but is not reporting statistical data

raymundbguinabo · April 11, 2026, 8:21am

I’m using a AllStarLink Node using Linode Cloud Server, Debian 12 OS and Allmon3. It shows currently registered in my Node Settings but my Node i.e 644081 is online but is not reporting statistical data.

I understand that this is similar or same to other topics however I tried all instructions but in no avail.

Maybe I overlook some Instructions...

K4QXN · April 11, 2026, 11:58am

I’m currently running two ASL3 nodes one on Debian 12 and the other on Debian 13 and I’m experiencing the same issue you described.
I first noticed the problem after the v1.8.1 update. At that time, both nodes were running Debian 12. One node updated to v1.8.1 and immediately stopped reporting data. The second node 59534 updated yesterday and is now showing the same issue.
I also upgraded my 621030 node to Debian 13 (Trixie), hoping the latest version would resolve the problem, but it’s still not reporting. I also verified my node password is correct in the rpt_http_registrations.conf. There are also no errors when I perform asl node auth checks Both nodes are otherwise functioning perfectly they’re just not reporting back to AllStarLink.

Hopefully, there’s a simple fix for this.

raymundbguinabo · April 11, 2026, 2:45pm

I also performed asl-node-auth-check and come up with the same result as you;

N8EI · April 11, 2026, 5:41pm

Do you have ‘statpost’ properly configured for each node? This is in rpt.conf.

K4QXN · April 11, 2026, 6:08pm

Thanks for responding N8EI. I do or what I think should be correct.

N8EI · April 11, 2026, 8:27pm

Hrm. Interestingly on the stats size, you're getting back an error of unauthorized. I see more of that than I should. I wonder if the stats system is locked up somehow. Looks like it's time for a restart.

N8EI · April 11, 2026, 8:56pm

Well, this was an interesting one that didn't come up in beta testing because I never thought to look... The newer version of Asterisk is now preferring IPv6 over IPv4 for all HTTP calls. Thus systems with IPv6 addresses were now choosing that causing a register-vs-actual IP mismatch causing the statpost to be ignored. I pulled the IPv6 address off the DNS name (which is sad). Sadly, fixing all the problems with statpost is not backwards compatible. But at some point we're going to have to rip off the bandaid as well.

K4QXN · April 11, 2026, 9:05pm

Thanks N8EI both node are online reporting now. I tried everything from my side to figure this out with no luck. Glad Raymund and I were able to help you find a potential flaw with the IP mismatch. Sorry to hijack your original post Raymund! 73’s from K4QXN

raymundbguinabo · April 12, 2026, 1:56am

When I check my Node Status now... Guess what? It automatically FIXED itself without doing anything. It seems that it is solved automatically by itself!!!

I will observed and update you K4QXN and my 73...