[ixpmanager] 404 on birdseye lock calls v7.2.0

[Pete Ashdown]

Sorry for the delay.  I made the changes to my route-collector script as described below and it is still not acquiring the lock.


> On Jun 23, 2026, at 4:45 AM, Thomas Kerin <thomas at islandbridgenetworks.ie> wrote:
> 
> Hi Pete,
> 
> We missed that script when releasing 7.2 - there’s an unreleased fix with the updated URL’s after the /admin prefixing changes.
> 
> Could you check if you made the following changes to the script already? See the highlighted section here:
> 
> https://github.com/inex/IXP-Manager/blob/main/tools/runtime/router-reconfigure-scripts/api-reconfigure-example-birdv2.sh#L43-L47
> 
> Hopefully it solves the problem. Let us know either way
> 
> Kind regards,
> Thomas Kerin
> 
> Island Bridge Networks Ltd
> https://www.islandbridgenetworks.ie/
> 
> 
> 
> 
> ------ Original Message ------
> From "Pete Ashdown via ixpmanager" <ixpmanager at inex.ie <mailto:ixpmanager at inex.ie>>
> To "INEX IXP Manager Users Mailing List" <ixpmanager at inex.ie <mailto:ixpmanager at inex.ie>>
> Cc "Pete Ashdown" <pashdown at xmission.com <mailto:pashdown at xmission.com>>
> Date 04/06/2026 19:50:28
> Subject Re: [ixpmanager] 404 on birdseye lock calls v7.2.0
> 
>> Thank you, Barry.  Best wishes to you as well.
>> 
>> I’m getting around to restricting /admin/ in NGINX and it is working well for my route-servers and as112, but my route-collectors are both getting “not available for update” when attempting to lock with IXP Manager.
>> 
>> Is this the final script that should be used for as112, route-collectors, and route-servers?
>> 
>> https://github.com/inex/IXP-Manager/tree/main/tools/runtime/router-reconfigure-scripts/
>> 
>>> On May 25, 2026, at 1:27 PM, Barry O'Donovan (INEX) <barry.odonovan at inex.ie> wrote:
>>> 
>>> 
>>> Hi Pete,
>>> 
>>> Hope you’re well.
>>> 
>>> I suspect you missed that all administrative URLs have been given a /admin prefix - see:
>>> 
>>> https://docs.ixpmanager.org/latest/install/security/#securing-administrative-functions
>>> 
>>> As a quick fix, you can try setting the following in your .env:
>>> 
>>> UNSECURED_API_ACCESS=1
>>> But this should be temporary.
>>> 
>>>  - Barry
>>> 
>>> 
>>> 
>>> 
>>> ------ Original Message ------
>>> From "Pete Ashdown via ixpmanager" <ixpmanager at inex.ie <mailto:ixpmanager at inex.ie>>
>>> To "INEX IXP Manager Users Mailing List" <ixpmanager at inex.ie <mailto:ixpmanager at inex.ie>>
>>> Cc "Pete Ashdown" <pashdown at xmission.com <mailto:pashdown at xmission.com>>
>>> Date 25/05/2026 17:45:54
>>> Subject [ixpmanager] 404 on birdseye lock calls v7.2.0
>>> 
>>>> Since upgrading to v7.2.0, I’m getting 404 errors on the attempts to lock the API for a router from birdseye. I can’t find any changes to the API that would do this. Am I missing something?
>>>>  
>>>> _______________________________________________
>>>> INEX IXP Manager mailing list
>>>> ixpmanager at inex.ie <mailto:ixpmanager at inex.ie>
>>>> Unsubscribe or change options here: https://www.inex.ie/mailman/listinfo/ixpmanager

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20260824/945a4d37/attachment-0001.htm>