-
Notifications
You must be signed in to change notification settings - Fork 200
Troubleshooting
This page helps you to solve a few common issues with IHP. Longterm we should find solutions for these issues, so that they don't appear every again. Until then, we have this page so that you can find a solution when you paste the error message into Google.
In case your problem cannot be solved with the steps on this page, join our awesome gitter community. We're happy to help!
Problem:
When you try to start a new ihp project by running ihp-new someproject, nix seems to start compiling a lot of haskell packages with ghc.
Solution:
This is most likely caused by a change we did to our binary cache. Run cachix use digitallyinduced to fix this.
warning: substituter 'https://digitallyinduced.cachix.org' does not have a valid signature for path ...
Problem:
When running ihp-new someproject to create a new project, nix seems to not use the binary cache with the above warning. Instead it tries to build all the packages itself, which takes hours.
Solution:
This is caused by a change we did to our binary cache. Open ~/.config/nix/nix.conf. There take a look at the trusted-public-keys = property. You should have two entries there (the public key of our old binary cache, and the new one). Remove the old one digitallyinduced.cachix.org-1:3mGU1b6u5obFp2VUfI55Xe8/+mawl7y9Eztu3rb94PI= (should be first of the two digitallyinduced keys). Then save the file and the problem is fixed.
Problem:
When you try to start a nix-shell, an error like this happens:
$ ./start
error: file '/build/db/.s.PGSQL.5432' has an unsupported type
Solution:
This happens because nix cannot deal the postgres unix socket which is in build/db. Usually this happens when the dev server of IHP is still running. Stop your IHP dev server and then try again.
When the dev server is not running, check that you have no postgres processes belonging to this unix socket running anymore. In case there are no processes running anymore, try to remove the file via rm -f.