Troubleshooting

find here the solution to most common issues you might run into when working with the engine browser debug p key debug colliders view invalid certificate errors in local environment as of this writing, the cert provided in the ir engine package for local use is not adequately signed browsers will throw up warnings about going to insecure pages you should be able to tell the browser to ignore it, usually by clicking on some sort of 'advanced options' button or link and then something along the lines of 'go there anyway' chrome sometimes does not show a clickable option on the warning if so, just type badidea or thisisunsafe when on that page you don't enter that into the address bar or into a text box, chrome is just passively listening for those commands allow instanceserver address connection via installing local certificate authority for more detailed instructions check https //github com/filosottile/mkcert https //github com/filosottile/mkcert short version (common for development process on ubuntu) execute sudo apt install libnss3 tools execute brew install mkcert (if you don't have brew, check it's page https //brew\ sh/ https //brew\ sh/ ) execute mkcert install navigate to /certs folder execute mkcert key file key pem cert file cert pem localhost 127 0 0 1 1 allow local file http server connection with invalid certificate open the developer tools in your browser by pressing ctrl+shift+i at the same time go to the 'console' tab and look at the message history if there are red errors that say something like get https //127 0 0 1 3030/socket io/?eio=3\&transport=polling\&t=nxlzlta net err cert authority invalid , then right click that url, then select 'open in new tab', and accept the invalid certificate allow instanceserver address connection with invalid certificate the instanceserver functionality is hosted on an address other than 127 0 0 1 in the local environment accepting an invalid certificate for 127 0 0 1 will not apply to this address open the dev console for chrome/firefox by pressing ctrl+shift+i simultaneously, and go to the console or network tabs if you see errors about not being able to connect to something like https //192 168 0 81 3031/socket io/?location=\<foobar> , right click on that url and open it in a new tab you should again get a warning page about an invalid certificate, and you again need to allow it accessdenied connecting to mariadb make sure you don't have another instance of mariadb running on port 3306 lsof i 3306 on linux, you can also check if any processes are running on port 3306 with sudo netstat utlp | grep 3306 the last column should look like \<id>/\<something you can kill any running process with sudo kill \<id> error listen eaddrinuse 3030 check which process is using port 3030 and kill killall 9 node or lsof i 3030 kill 3 \<proccessidfrompreviouscommand> 'cors error' in terminal try accessing the page using https //localhost 3000 instead of https //127 0 0 1 3000 default blank screen try typing “thisisunsafe” or "iknowwhatiamdoing" then reload page instanceserver or resource loading error? open dev console, click on the get link in new tab and accept certificate by typing thisisunsafe” or "iknowwhatiamdoing" then reload original page to install a new package for editor react components in monorepo type in terminal npm i \<packagename> w @ir engine/packages/editor using local storage instead of minio currently minio is used as default storage for local development if you want to use local storage then do following steps set vite file server to the commented values under # use following value for local file server and comment out the values above it set storage provider to local accessing minio s3 storage provider running in local docker using https //min io/docs/minio/linux/administration/minio console html when minio contain is running in your docker, navigate to https //localhost 9001/ https //localhost 9001/ in your browser make sure to accept invalid certificate warning login using username as server and password as password you can find these credentials in scripts/docker compose yml as minio root user & minio root password using https //s3browser com/ (windows only) download & install s3 browser from https //s3browser com/download aspx https //s3browser com/download aspx launch and connect using following details clear all data from minio s3 storage provider running in local docker run following commands in your terminal docker container stop etherealengine minio s3 docker container rm etherealengine minio s3 docker container prune force docker volume prune force npm run dev docker npm run dev reinit db not seeding routes (e g error no project installed please contact site admin) try npm run dev reinit or docker container stop ir engine db docker container rm ir engine db docker container prune force npm run dev docker npm run dev reinit weird issues with your database? try npm run dev reinit or if on windows npm run dev reinit windows