[ixpmanager] Assistance with Birdseye and HTTP 500 Error

[Michel Blais]

Hi,

I'm new to IXP manager and would need help with birdseye.

I've installed the route server, which appears to be functioning correctly.
However, I'm having trouble getting Birdseye to work—it consistently
returns an HTTP 500 error. I've reviewed the documentation and watched the
setup video multiple times. I've also searched through the mailing list
archives back to 2020, but none of the issues discussed there seem to match
what I'm encountering.

Here are some details about my setup:

Distro: Debian 12
Bird: Version 2.17 (built from source)

Birdseye:
Initially tried version 2.0 with PHP 8.2 from the Debian repository
Then installed PHP 8.3 from the sury.org repository and tried Birdseye 2.1
Also tried PHP 8.4 briefly but encountered many deprecated warnings in the
Lighttpd logs, so I reverted to 8.3
Birdseye is installed in /opt/birdseye-v2.1.0, with a symbolic link
/opt/birdseye pointing to it

Despite these efforts, I continue to receive a 500 error when accessing
Birdseye.

My .env file for the route server looks like this:
cat birdseye-rs1-cabId-dcName-ipv4.env
IRDC="/usr/bin/sudo /usr/local/sbin/birdc -s
/var/run/bird/bird-rs1-cabId-dcName-ipv4.ctl"

CACHE_DRIVER=file

LOOKING_GLASS_ENABLED=true

The www-data user is able to successfully run Bird commands via the CLI:
su -l www-data -s /bin/bash
/usr/bin/sudo /usr/local/sbin/birdc -s
/var/run/bird/bird-rs1-cabId-dcName-ipv4.ctl "show status"

BIRD 2.17 ready.

BIRD 2.17

Router ID is x.y.z.253

Hostname is rs1.cabId.dcName

Current server time is 2025-04-20 09:16:37

Last reboot on 2025-04-14 19:08:00

Last reconfiguration on 2025-04-20 09:15:01

Daemon is up and running

but I had to remove the "-2" because this option doesn't seem to be
supported anymore in bird 2.17.
www-data at rs1:~$ /usr/bin/sudo /usr/local/sbin/birdc -2 -s
/var/run/bird/bird-rs1-cabId-dcName-ipv4.ctl "show status"
/usr/local/sbin/birdc: invalid option -- '2'
Usage: /usr/local/sbin/birdc [-s <control-socket>] [-v] [-r] [-l]

The journal doesn't show any error. With the config provided in the git
repo, "journalctl -t lighttpd" was showing warnings about depreciated
modules so I've started back from debian default config file and added the
server.bind and the document root to /opt/birdseye/public. No warning
anymore but still the same issue.

I also followed the GitHub documentation and video instructions to set
proper permissions on the storage folder and even tried changing ownership
of the entire Birdseye directory to www-data, just in case. Unfortunately,
this didn't resolve the issue either.

Lastly, I saw on the mailing list archive a recommendation to check Laravel
logs. I found a log entry in storage/logs related to an undefined
HTTP_HOST, which appeared when I tried running index.php from the PHP CLI,
but nothing that directly explains the 500 error when accessing through the
browser.

I'm wondering if the unsupported -2 flag might be related to the issue? Any
insights or suggestions would be greatly appreciated.

Thank you in advance for your help!
-- 
Cordialement, / With regards,

Michel Blais
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20250423/17ef11f5/attachment.htm>