<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Apr 10, 2025, at 3:28 AM, Barry O'Donovan (INEX) via ixpmanager <ixpmanager@inex.ie> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><div x-em-quote="" style="font-family: "Avenir Next"; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class="Apple-interchange-newline"><br></div><div id="xa1f4acdb7696449" style="caret-color: rgb(0, 0, 0); font-family: "Avenir Next"; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><blockquote cite="x-msg://36/433BCCF1-C39D-41B6-856F-0325757A3612@xmission.com" type="cite" class="cite2" style="margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right: 0px; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); margin-top: 3px; padding-top: 0px;">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:</blockquote><div id="xa1f4acdb7696449" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br></div><div id="xa1f4acdb7696449" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">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.</div><div id="xa1f4acdb7696449" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br></div><div id="xa1f4acdb7696449" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">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.</div></div></div></blockquote><div><br></div>Do you have a reference to your NGINX config? The other bug I opened and closed, also changed behavior between Apache and NGINX, in regards to embedded images.</div><div><br></div><div><blockquote type="cite"><div><div id="xa1f4acdb7696449" style="caret-color: rgb(0, 0, 0); font-family: "Avenir Next"; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br><blockquote cite="x-msg://36/433BCCF1-C39D-41B6-856F-0325757A3612@xmission.com" type="cite" class="cite2" style="margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right: 0px; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); margin-top: 3px; padding-top: 0px;"><div><div>500</div><div>Server Error :: Client error: `POST<span class="Apple-converted-space"> </span><a href="https://auth.peeringdb.com/oauth2/token/%60">https://auth.peeringdb.com/oauth2/token/`</a><span class="Apple-converted-space"> </span>resulted in a `401 Unauthorized` response: {"error": "invalid_client”}</div></div></blockquote><div id="xa1f4acdb7696449" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br></div>I tested our own INEX install here with PeeingDB Oauth and it worked fine.</div><div id="xa1f4acdb7696449" style="caret-color: rgb(0, 0, 0); font-family: "Avenir Next"; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br></div><div id="xa1f4acdb7696449" style="caret-color: rgb(0, 0, 0); font-family: "Avenir Next"; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">The above error looks like it’s coming from PeeringDB and the ‘<span>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.</span></div></div></blockquote><br></div><div>I’ll inquire with them. What about the algorithm choice? Should all of them work?</div><div><br></div><br></body></html>