[ixpmanager] PeeringDB login

[Barry O'Donovan (INEX)]

>I found the problem with PeeringDB OAuth.  If you go to the OAuth and look at the settings for your current key, what they display for the “Client Secret” is a hash of the secret, and not the actual secret.  You need to create a new key in order to get the actual “Client Secret” because they won’t display it again for you.
>
>As for algorithm “No OIDC Support” works fine.
>
>I’d still like to know why NGINX is acting differently from Apache.
>

On a standard install, there should be no issues.  Apache is 
considerably easier than Nginx which is why we default to that in the 
documentation / installers.

With Apache, you install the Apache PHP module (e.g., 
libapache2-mod-php8.0) and PHP scripts tend to “just work”. With Nginx, 
you need to install, e.g., php8.0-fpm, which runs as its own process and 
then you need to configure Nginx to pass PHP requests off to that 
daemon.

On systems running the latest 6.x release of IXP Manager and Nginx, I 
could not replicate your issue. As such, and because I use Nginx all the 
time also, I’d be fairly confident this is a local issue of some sort.

I do note from your issues that you are running php 8.3. I only run 
php8.0 or php8.1 with IXP Manager v6.x. I’m not suggesting there would 
be an issue with 8.3, I just simply do not know.

As for the standard development config, it’s really basic:

         root /srv/ixpmanager/public;
         index index.php;

         location / {
                 try_files $uri $uri/ /index.php?$query_string;
         }

         location ~ \.php$ {
                 include snippets/fastcgi-php.conf;
                 fastcgi_pass unix:/run/php/php8.1-fpm.sock;
         }

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