[Help] Virtual Box / PHP

[Yann75]

Hi,

I have a brand new TOS 6 6.0.694 installation and I tried to Virtual Box official package 7.0.2..0.1012. Installation took a while (for a few minutes, VirtualBox appeared in the Application Launcher but not in the list of installed packages)

When I try to access the interface, I received the PHP error message already referenced in some other threads but not suggestion works.

An unknown PHP error occurred. This is most likely a syntax error in config.php in phpVirtualBox's folder. The most common errors are an unclosed quote or a missing semicolon in a configuration item that has been entered (e.g. location, username, or password).

Depending on your PHP configuration, navigating directly to config.php in your web browser may display the PHP error message.

A click on the link (/virtualbox/config.php) in the error message lands on another error:
502 Bad Gateway
nginx/1.18.0 (Ubuntu)

The php-fpm.conf file seems ok, with my account configured in the listen.user and listen.group.

Any suggestion / fix ?

Thanks

[Yann75]

Done some debugging
1/ Not sure why php-fpm was not running. Started it manually, not sure if it will come back automatically after reboot (can't do it now)
2/ There are errors in the Nginx configuation file: the path to unix sock file in nginx.conf and php-fpm.conf refer to unix:/run/php/php-fpm.sock but unix:/run/php/php7.4-fpm.sock seems to be the correct path

After manually "fixing", I get the login / password screen of VBox ... but admin/admin mentioned in the installation details doesn't work

[TMzethar]

Hi.
This may help you solve the issue:
viewtopic.php?t=5858

[Yann75]

Thanks. Unfortunately I have a different issue. The user/group where properly set to my username, not root. Also the /etc/init.d/php-fpm no longer exists, probably a change with TOS 6

[TMzethar]

Thank you for providing more information, it is clear that this is a new phenomenon.
Please first observe if there is RAID synchronization or unusually high CPU/RAM usage.
Try restarting the NAS to attempt to restore normal operation.
If the issue persists, we recommend contacting Live Chat to schedule an engineer for remote troubleshooting.