Closed dimamarkus closed 1 year ago
The issue here is not the assigned port... you need to shell into the app and run a command to build the admin panel.
Also set it to development mode too.
npm run build
Our code actually keeps the port as 1337 internally since we set the target port to 1337... the expose port can be anything you want 1337 or over 9000.
Join our discord if you want to chat about apps or get help faster in our support channel ;)
You might have some issues fsnotify you can resolved, plenty of threads on that in our discord.
Our min requirements for our apps is for the app pool to have an ssd or hdd with a special metadata vdev(ssd). Read more here.
@xstar97
Hi. Thank you for your reply.
npm run build
instructions but the result is the same error. The console mentions the CSRP. Maybe that is the issue?@xstar97
Hi. Thank you for your reply.
- My server meets the minimum requirements and im running many others apps successfully through TrueCharts.
- I have followed your
npm run build
instructions but the result is the same error. The console mentions the CSRP. Maybe that is the issue?
My apologies, did you turn the app off and then back on afterwards?
This might be better conversation for our discord 😅.
✅ SOLUTION:
Running npm run build
inside the shell of the app container, followed by a restart of the App from TrueNAS UI solved this issue for me even with the default port 1337.
@xstar97 can you add the restart to docs?
This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists
App Name
strapi
SCALE Version
22.12.0
App Version
4.6.1_8.0.29
Application Events
Application Logs
Application Configuration
Describe the bug
By default, Strapi runs on port 1337. This TrueNAS chart App leaves that default configuration. The problem is that TrueNAS requires app containers to expose ports 9000 and above. If I change the exposed port of the container (to 10337 for example), the app boots up but because of some internal configuration still has code pointing to port '1337'. Attempting to pass in a configuration ENV variable into the container to fix this yields the error submitted here.
To Reproduce
Expected Behavior
I expected the apps internal API calls to the database to match the PORT I assigned.
Screenshots
Additional Context
*
I've read and agree with the following