<html><head>
<style id="css_styles" type="text/css"><!--blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; }
a img { border: 0px; }
li[style='text-align: center;'], li[style='text-align: center; '], li[style='text-align: right;'], li[style='text-align: right; '] { list-style-position: inside;}
body { font-family: 'Avenir Next'; font-size: 10.5pt; }
.quote { margin-left: 1em; margin-right: 1em; border-left: 5px #ebebeb solid; padding-left: 0.3em; }
a.em-mention[href] { text-decoration: none; color: inherit; border-radius: 3px; padding-left: 2px; padding-right: 2px; background-color: #e2e2e2; }
._em_placeholder {color: gray; border-bottom: 1px dotted lightblue;} ._em_placeholder:before{color:gray; content: '{{ ';} ._em_placeholder:after{color:gray; content: ' }}';}
--></style></head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div style="color: rgb(0, 0, 0);"><br /></div>
<div style="color: rgb(0, 0, 0);"><br /></div>
<div id="x3c36d817881d40f" class="plain"><blockquote cite="8286A950-1BA4-41B0-9CA7-682BD4E00CC1@xmission.com" type="cite" class="cite2" style="color: rgb(0, 0, 0);">
<div class="plain_line">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.</div>
<div class="plain_line"> </div>
<div class="plain_line">As for algorithm “No OIDC Support” works fine.</div>
<div class="plain_line"> </div>
<div class="plain_line">I’d still like to know why NGINX is acting differently from Apache.</div>
<div class="plain_line"><br /></div></blockquote><div><br /></div><div>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.</div><div><br /></div><div>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.</div><div><br /></div><div>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.</div><div><br /></div><div>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.</div><div><br /></div><div>As for the standard development config, it’s really basic:</div><div><br /></div><div> root /srv/ixpmanager/public;</div><div> index index.php;</div><div><br /></div><div> location / {</div><div> try_files $uri $uri/ /index.php?$query_string;</div><div> }</div><div><br /></div><div><span> location ~ \.php$ {</span></div><div> include snippets/fastcgi-php.conf;</div><div> fastcgi_pass unix:/run/php/php8.1-fpm.sock;</div><div> }</div><div><br /></div><div><br /></div><blockquote cite="8286A950-1BA4-41B0-9CA7-682BD4E00CC1@xmission.com" type="cite" class="cite2" style="color: rgb(0, 0, 0);"><div class="plain_line"></div>
</blockquote></div>
</body></html>