ReadyNAS Pro 6 on readyos v6.10.6 no frontview on boot

First of all let me right of the bat start by acknowledge that I'm aware I'm running "unsupported" software on legacy hardware.

My setup has been working good for years and years since I due to security concerns and the limitations of the old v4.x.x got new hard drives and upgraded to ReadyNAS OS v6 around versions 6.2.x.

I've been running on this old trusty ReadyNAS Pro 6, updating one OS release at a time for a long time and not really caring that at some point an OS update broke the startup sequence somehow. 

For some unknown reason the apache2 service doesn't properly start on boot, so no Frontview.

● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since ons 2021-12-01 02:16:19 EET; 3min 18s ago
  Process: 4867 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS)
  Process: 4757 ExecStop=/frontview/bin/fvapps (code=exited, status=0/SUCCESS)
 Main PID: 3152 (code=killed, signal=SEGV)

dec 01 02:16:18 ReadyNAS-2 systemd[1]: Starting The Apache HTTP Server...
dec 01 02:16:19 ReadyNAS-2 apachectl[4751]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 192.168.66.101. Set the 'ServerName' directive globally to suppress t
his message
dec 01 02:16:19 ReadyNAS-2 apachectl[4751]: httpd (pid 4640) already running
dec 01 02:16:19 ReadyNAS-2 apachectl[4867]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 192.168.66.101. Set the 'ServerName' directive globally to suppress t
his message
dec 01 02:16:19 ReadyNAS-2 systemd[1]: Started The Apache HTTP Server.

So, ssh in to the server, and quickly types 'sudo service apache2 restart' and voila, 

● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
   Active: active (running) since ons 2021-12-01 02:21:11 EET; 3min 37s ago
  Process: 5372 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
  Process: 5265 ExecStartPre=/frontview/bin/fvapps (code=exited, status=0/SUCCESS)
 Main PID: 5380 (/usr/sbin/apach)
   CGroup: /system.slice/apache2.service
           ├─5380 /usr/sbin/apache2 -k start
           ├─5381 apache_log               
           ├─5382 apache_log               
           ├─5398 /usr/sbin/apache2 -k start
           ├─5399 /usr/sbin/apache2 -k start
           ├─5400 /usr/sbin/apache2 -k start
           ├─5401 /usr/sbin/apache2 -k start
           ├─5402 /usr/sbin/apache2 -k start
           ├─5403 /usr/sbin/apache2 -k start
           ├─5414 /usr/sbin/apache2 -k start
           ├─5415 /usr/sbin/apache2 -k start
           ├─5416 /usr/sbin/apache2 -k start
           ├─5503 /usr/sbin/apache2 -k start
           └─5549 /frontview/lib/dbbroker.cgi

dec 01 02:21:11 ReadyNAS-2 systemd[1]: Starting The Apache HTTP Server...
dec 01 02:21:11 ReadyNAS-2 apachectl[5372]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 192.168.66.101. Set the 'ServerName' directive globally to suppress t
his message
dec 01 02:21:11 ReadyNAS-2 apache2[5376]: [ssl:warn] [pid 5376] AH01909: 192.168.66.101:443:0 server certificate does NOT include an ID which matches the server name
dec 01 02:21:11 ReadyNAS-2 systemd[1]: Started The Apache HTTP Server.

Strange thing is that I haven't found any other issues. Network shares and really every other add-on I've installed works on boot so it's not a big issue, just an annoyance but if anyone has suggestions I'd love to hear them! 🤔