[ixpmanager] PeeringDB login

[Barry O'Donovan (INEX)]

>I just switched back to Apache from NGINX on a hunch.  That fixed the 
>second problem with creating new user accounts, and the PeeringDB error 
>is a bit more explicit now:

I can’t imagine that there’d generally be an issue on different web 
servers, and I’d suspect something more to do with local settings.

I develop on Nginx on my Mac, Apache on Vagrant. We run on Apache in 
production but this is fronted by an Nginx SSL concentrator and a 
Varnish pipe.



>500
>Server Error :: Client error: `POST 
>https://auth.peeringdb.com/oauth2/token/` resulted in a `401 
>Unauthorized` response: {"error": "invalid_client”}

I tested our own INEX install here with PeeingDB Oauth and it worked 
fine.

The above error looks like it’s coming from PeeringDB and the 
‘invalid_client’ might indicate you don’t have your IXP Manager 
correctly set up on PeeringDB or you’ve used the wrong tokens on the IXP 
Manager side maybe? Really it’s a question for PeeringDB.

   - Barry

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20250410/ea422423/attachment.htm>