I have cloned a site directly from Kinsta into a new install of DevKinsta however it is not loading correctly. The css and js files are not loading and a 403 is returned for the parent folder where these files are located. This folder is \wsl.localhost\docker-desktop\mnt\docker-desktop-disk\data\docker\volumes\DevKinsta\public\outcomes\wp-content\themes\open-theme\assets\dist\frontend
The site uses a theme built with composer so I have followed the instructions here: Support for Composer - #14 by Olivier_Bigras to install composer and here: Install Node and Gulp to install node into the Docker Container however that has not fixed the problem.
The source code shows where as on the live site it showns The same applies to the JS file.
What else do I need to do so DevKinsta will load the files as outlined in manifest.json in the frontend folder location?
HI Vladimir, thanks for your assistance. I am pulling this site directly from Kinsta and it is working perfectly there. I have not changed anything about the site or the theme files at all except the config details to make it work on DevKinsta. I can see some errors in the main log which relate to json parsing and syntax however this theme is working on Kinsta itself.
Can you please take a look at the log file (I created a fresh one) and let me know your thoughts?
Hello @nicolepaton
I checked the log and there are 2 different types of JSON-related errors. The ‘SyntaxError: Unexpected non-whitespace character after JSON…’ is not the cause, we’ve seen it before even in sites that work fine.
The other one’s I’m curious about like: “SyntaxError: Unexpected token ‘/’, “/docker/vo”…” are different but non-specific at the moment.
Please try the following:
Fix permissions
With DevKinsta and Docker running, please go to Command line and run these two:
Refresh without cache, or in incognito tab and check.
Run ‘build’ in theme directory
You stated you already installed composer and node, but I’m not sure if you ran build and if you installed it in theme directory. If you haven’t, follow all steps, if not, just the ones for build.
Go to Terminal and run:
docker exec -it devkinsta_fpm bash
navigate to theme directory by running: cd /www/kinsta/public/outcomes/wp-content/themes/open-theme
skip first two if you already installed them in your theme directory:
composer install npm install npm run build
You also should try resetting permalinks. In the WordPress admin area, go to Settings > Permalinks and click Save Changes to refresh routing rules.
Since we are troubleshooting blind, there might be some back and forth, and I’m not sure these steps would work, but please try that.
Thanks very much for your detailed assistance. I have done step 1 and that did not work to fix the theme. It still looks the same.
I have tried to do step 2, however I’m getting stuck at the composer install step. It does not appear to be available to install despite the fact that I did follow the steps outlined in the other thread: Support for Composer - #10 by DavidME . In that case I had installed in the tmp folder as per that thread. So this time when your steps above did not work I tried to follow the same steps again in the theme folder. Got through the install but the theme doesn’t have a package.json file and I’m not the original developer so I’m a bit unsure where to go from here. It still isn’t running in the browser in the same way as it does live on Kinsta where it also doesn’t have the package.json file.
Here is my terminal log:
root@bffba833335a:/tmp# composer install
bash: composer: command not found
root@bffba833335a:/tmp# cd /www/kinsta/public/outcomes/wp-content/themes/open-theme
root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# composer install
bash: composer: command not found
root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# php -r “copy(‘https://getcomposer.org/installer’, ‘composer-setup.php’);”
root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# php -r “if (hash_file(‘sha384’, ‘composer-setup.php’) === ‘c8b085408188070d5f52bcfe4ecfbee5f727afa458b2573b8eaaf77b3419b0bf2768dc67c86944da1544f06fa544fd47’) { echo ‘Installer verified’; } else { echo ‘Installer corrupt’; unlink(‘composer-setup.php’); } echo PHP_EOL;”
Installer verified
root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# php composer-setup.php
All settings correct for using Composer
Downloading…
Composer (version 2.10.3) successfully installed to: /www/kinsta/public/outcomes/wp-content/themes/open-theme/composer.phar
Use it: php composer.phar
root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# composer install
bash: composer: command not found
root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# php composer.phar install
Composer could not detect the root package (*ogdev/open-theme) version, defaulting to ‘1.0.0’. See Troubleshooting - Composer
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run composer update or composer update <package name>.
Nothing to install, update or remove
Generating autoload files
root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# npm install
npm WARN saveError ENOENT: no such file or directory, open ‘/www/kinsta/public/outcomes/wp-content/themes/open-theme/package.json’
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open ‘/www/kinsta/public/outcomes/wp-content/themes/open-theme/package.json’
npm WARN open-theme No description
npm WARN open-theme No repository field.
npm WARN open-theme No README data
npm WARN open-theme No license field.
npm notice This endpoint is being retired. Use the bulk advisory endpoint instead. See the following docs for more info: npm Registry API
up to date in 0.362s
found 0 vulnerabilities
root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# npm run build
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /www/kinsta/public/outcomes/wp-content/themes/open-theme/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open ‘/www/kinsta/public/outcomes/wp-content/themes/open-theme/package.json’
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2026-09-10T07_27_27_548Z-debug.log
root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme#
I think I had this all wrong the entire time, it just occurred to me that this theme is using HTTP URL instead of file paths to read directly from the disk in one of the configuration files. Strictly speaking, this is outside of our scope of service in both forum or support chats, but I had to test on my end and it worked by replacing the code. I’ll send you the new code in DM.
What to do:
Find the theme-general.php file in /wp-content/themes/open-theme/inc
