It seams that script are only usable in the portal when they are in the Script directory without nested folders.
steps to reproduce:
create a script
add configuration for portal
check script in portal - works
create sub folder for scripts
move script to sub folder and adjust settings
check in portal - Script not found - same with portal pages

(idk if it is relevant but i set a script folder)

Best, Dy
Hello Dy,
Thank you for the clear steps, they made this easy to follow.
I reproduced it in our lab on the same image you mentioned in your earlier Portal report, devolutions/powershell-universal:2026.3.3-ubuntu-24.04. A script at the top level of the script folder opens in the Portal, but a script in a subfolder shows "Not Found", both from its Open button on the Services page and inside a Portal page that shows it with a Script Form widget. Setting the Script Base Folder to Scripts/, as you have, made no difference.
This is a defect in how the Portal looks up a script that sits in a subfolder, and I have documented it with these steps for follow-up. For now, keeping the scripts you need in the Portal at the top level of the script folder is the setup that works.
If you have moved to another version or image since that report, please tell me which one, so I can check it there too.
Best regards,
Michel
Michel Audi