Hi everyone,
I am currently working on updating and maintaining Node.js support for HestiaCP v1.10.4.
As some of you might have experienced, the original repository JLFdzDev/hestiacp-nodejs is no longer compatible with recent HestiaCP releases. After installing it, clicking on the “Quick Install App” menu immediately triggers a 500 Internal Server Error in the control panel.
I also tested the updated fork trustos/hestiacp-nodejsv2, but it encounters the exact same 500 Internal Server Error on v1.10.4.
To resolve this issue and bring full compatibility to HestiaCP 1.10.x, I have created a new fork for further development:
Repository: addrmwn/hestiacp-nodejs
Issue Details & Discussion
It appears that structural updates or routing changes in HestiaCP v1.10.4 broke how custom Quick App Installer scripts register their templates and PHP backends.
I would appreciate any insights from the core team or community:
-
What key changes were made to the Quick App Installer structure or web UI scripts in v1.10.4 that could cause a 500 error when external app templates are hooked into
/usr/local/hestia/web/? -
Are there specific panel PHP logs or debug steps recommended for tracing 500 errors inside the Hestia web engine besides checking
/var/log/hestia/nginx-error.log? -
Has anyone successfully adapted custom Quick App installers for 1.10.x?
If anyone is interested in testing or contributing to fix this compatibility gap, feel free to check the repository or discuss here!
Thank you!