[Spce-user] ISSUE: mr14.0.1 peer_auth_register: Internal Server Error

[SPCE Newbie]

Attempting to toggle "Enable Peer Authentication"

/ngcp-data/logs/api.log:

Dec 22 16:23:19 azlan2 ngcp-panel: INFO: IP=192.168.1.119
CALLED=API[PATCH]/api/subscriberpreferences/4 TX=188392E6E76D22C8
USER=administrator DATA=«{}» MSG=""
LOG="«[{"op":"add","path":"/peer_auth_register","value":true}]»"
DURATION=0.013595 Dec 22 16:23:19 azlan2 ngcp-panel: INFO:
IP=192.168.1.119 CALLED=API[PATCH 500]/api/subscriberpreferences/4
TX=188392E6E76D22C8 USER=administrator DATA=«{}»
MSG="«{"code":500,"message":"Internal Server Error."}»" LOG="«Failed
to add peer registration on application servers»" DURATION=0.166719


/ngcp-data/logs/sems.log:

Dec 22 16:32:01.840831 spce ngcp-sems[19802]: [#7fd6fd1c26c0]
[createDBRegistration, DBRegAgent.cpp:956] ERROR:  MySQL++ error: Cannot add or update a child row: a foreign key constraint fails (`kamailio`.`sems_registrations`, CONSTRAINT `sub_id_ref` FOREIGN KEY (`subscriber_id`) REFERENCES `subscriber` (`id`) ON DELETE CASCADE ON UPDATE CASCADE)
Dec 22 16:32:01.840953 spce ngcp-sems[19802]: [#7fd6fd1c26c0]
[updateDBRegistration, DBRegAgent.cpp:1039] WARNING:  updating registration in DB with query 'update sems_registrations set last_code=200, last_reason='Ok', registration_status=2, last_registration=NOW(), expiry=TIMESTAMPADD(SECOND,0, NOW()), contacts='<sip:ngcp-lb at 198.51.100.0:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=21600' where subscriber_id=2;' failed: 'Rows matched: 0  Changed: 0  Warnings: 0'
Dec 22 16:32:01.854526 spce ngcp-sems[19802]: [#7fd6f17fa6c0] [invoke,
DBRegAgent.cpp:1604] WARNING:  REGISTER: Type of the registration object is undefined.
Dec 22 16:32:01.854540 spce ngcp-sems[19802]: [#7fd6f17fa6c0]
[handleRegistrationTimer, DBRegAgent.cpp:531] WARNING:  Registration for subscriber with ID 5 already exists, removing.
Dec 22 16:32:01.941863 spce ngcp-sems[19802]: [#7fd6fd1c26c0]
[createDBRegistration, DBRegAgent.cpp:956] ERROR:  MySQL++ error: Cannot add or update a child row: a foreign key constraint fails (`kamailio`.`sems_registrations`, CONSTRAINT `sub_id_ref` FOREIGN KEY (`subscriber_id`) REFERENCES `subscriber` (`id`) ON DELETE CASCADE ON UPDATE CASCADE)
Dec 22 16:32:01.942740 spce ngcp-sems[19802]: [#7fd6fd1c26c0]
[updateDBRegistration, DBRegAgent.cpp:1039] WARNING:  updating
registration in DB with query 'update sems_registrations set
last_code=200, last_reason='Ok', registration_status=2,
last_registration=NOW(), expiry=TIMESTAMPADD(SECOND,0, NOW()),
contacts='<sip:ngcp-lb at 198.51.100.0:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=21600'
where subscriber_id=2;' failed: 'Rows matched: 0  Changed: 0  Warnings:
0'

Foreign key contstraint error is streaming continuously filling logs.

Type of object is undefined and registration for subscriber with ID 5
already exists warnings happens on attempting to toggle-on.

Kind regards


----- Original Message -----
Date: Mon, 22 Dec 2025 16:17:57 +0100
From: Jose Antonio Su Ng <jsung at sipwise.com>
To: SPCE Newbie <spce-user at tel.co.uk>
Cc: "spce-user at lists.sipwise.com" <spce-user at lists.sipwise.com>
Subject: Re: [EXTERNAL] RE: [Spce-user] ISSUE: mr14.0.1
peer_auth_register: Internal Server Error


  Hello,

Hmm.. can you provide the output from api.log and sems.log in verbose?

Note: Please don't forget to always include spce-user at lists.sipwise.com 
in your replies to the mail.

Best regards,
On 12/22/25 15:10, SPCE Newbie wrote:
> Hello Jos, Thank you.  I appreciate you helping over the holidays.
>
> ERROR: Failed XML-RPC call to appserver: $VAR1 = [#012 [#012 7,#012
> 1,#012 '<?xml  
> version="1.0"?>#015#012<methodResponse><params><param>#015#012#011<value><array><data><value><i4>200</i4></value><value>OK</value></data></array></value>#015#012</param></params></methodResponse>#015#012'#012
> ],#012 [#012 8,#012 -1,#012 ''#012 ]#012 ];
> Dec 22 14:46:28 azlan2 ngcp-panel: ERROR: Failed to set peer
> registration:  Failed to add peer registration on application servers
>
> Installed package list attached.
>
> Panel restarted tail -f ollowing panel.log.  (Restart not logged).
> Attempting to toggle after the restart errors in the same way.
>
> Kind regards
>
>
> ----- Original Message -----
> Date: Mon, 22 Dec 2025 14:33:54 +0100
> From: Jose Antonio Su Ng<jsung at sipwise.com>
> To: SPCE Newbie<spce-user at tel.co.uk>,spce-user at lists.sipwise.com
> Subject: Re: [EXTERNAL] [Spce-user] ***SPAM*** ISSUE: mr14.0.1
> peer_auth_register: Internal Server Error
>
>
> Hello,
>
> I cannot replicate your issue. Can you check what error you get on
> api/panel logs when you set the toggle to "ON"?
>
> What is the package version that you have installed? Have you tried
> restarting ngcp-panel to see if issue persist?
>
> Best regards,
> On 12/21/25 20:40, SPCE Newbie wrote:  
>> Happy Christmas fellow spce-users,
>>
>> 1.  Expected Behaviour
>>
>> With all Peers created under 13.5.1 deleted, first 14.0.1 Peer
>> created: Working top to bottom in the UI:
>> - skip peer_auth_hf_user and commit
>> - populate peer_auth_pass and commit
>> - populate peer_auth_realm and commit
>> - skip peer_auth_register for now
>> - populate peer_auth_registrar_server and commit
>> - populate peer_auth_user and commit
>> - circle back to, and toggle peer_auth_register, on
>>
>> Successful configuration achieved.
>>
>>
>> 2.  Observed Behaviour
>>
>> With all Peers created under 13.5.1 deleted, first 14.0.1 Peer
>> created: Working top to bottom in the UI:
>> - skip peer_auth_hf_user and commit
>> - populate peer_auth_pass and commit
>> - populate peer_auth_realm and commit
>> - skip peer_auth_register for now
>> - populate peer_auth_registrar_server and commit
>> - populate peer_auth_user and commit
>> - circle back to, and toggle peer_auth_register, on
>>
>> Enable Peer Authentication will not toggle-on -- errors per the
>> subject.
>>
>>
>> 3.  Attempted Resolution
>>
>> Peers created under 13.5.1 with peer_auth_hf_user populated could not
>> be made to work.
>>
>> Under 14.0.1 Peers created using peer_auth_user (as fellow spce-user
>> did).
>>
>>
>> 4.  Remarks
>>
>> Credentials clearly fictitious. Same error observed with valid
>> credentials.  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20251222/21ba6a26/attachment-0001.htm>