# Just "errors" when I try to run DevKinsta on ubuntu 20.04LTS **URL:** \ **Category:** Bug Reports\ **Created:** [April 16, 2024, 3:11pm UTC](https://community.kinsta.com/t/just-errors-when-i-try-to-run-devkinsta-on-ubuntu-20-04lts/3308 "2024-04-16T15:11:04Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![Dumitru\_Galit](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/dumitru_galit/32/3258_2.png) [@Dumitru\_Galit](https://community.kinsta.com/u/Dumitru_Galit)\ **Post date:** [April 17, 2024, 10:29am UTC](https://community.kinsta.com/t/just-errors-when-i-try-to-run-devkinsta-on-ubuntu-20-04lts/3308/9 "2024-04-17T10:29:33Z")
Nothing more to add on this thing. Just will confirm that I was able to launch the DevKinsta almost properly (for some reason the downloaded project was assigned to an non-existand user in my local files ~/DevKinsta/public/mywebsitedomain which didn’t allow DevKinsta run to edit the wp-config.php file - so just chmod 777 and retry just solved the whole issue. And now it works. Had another issue with the certificate but I discussed it here: [SSL issues (one resolved, one not) - #8 by Dumitru\_Galit](https://community.kinsta.com/t/ssl-issues-one-resolved-one-not/3235/8) You might want to make the .pem file for your certification easier to find so nobody is forced to generate his personal CA to access the local instance. Not generating a certificate would probably be even better because it would allow you to just to “proceed unsafe” while for some reason chrome thinks a unrecognized Certificate is worse than a nonexistent one while still using https - the more you live… --- _[View the full topic](https://community.kinsta.com/t/just-errors-when-i-try-to-run-devkinsta-on-ubuntu-20-04lts/3308)._