Common Issues and Solutions
Issue: When running some commands such as git clone or curl you receive an error like "SSL certificate problem: unable to get local issuer certificate"
Solution: Run the following command from an administrator Git Bash prompt in your "portlandor" directory:
cat cop_ca.pem >> /mingw64/ssl/certs/ca-bundle.crt
Issue: After your Windows password is changed, Docker cannot access any files. In the worst case, Docker may repeatedly try to access the disk with the old password and cause your account to be locked due to too many failed login attempt.
Solution: In Docker settings, go to "Shared Drives". Click on "Reset Credentials" to put in the new password.
Issue: After lando rebuild or lando start, the URL for http://portlandor.lndo.site remains red, which means the address cannot be reached. This can happen when your PC is offline or the domain name cannot be resolved.
Solution: Add an entry 127.0.0.1 portlandor.lndo.site in your hosts file. More info here
Issue: Get an error during lando rebuild. Or the drush not found error when trying to run lando drush.
[ErrorException]
file_put_contents(./composer.json): failed to open stream: Permission denied
Solution: Run lando start after the failed lando rebuild seems to fix this problem. This appears to be a bug introduced since lando v40. See the open bug here. There is a workaround at the bottom of that page: add a line in your .lando.yml to set permissions on that folder and run lando rebuild again.
Issue: After updating your local repo, the site won't come up. You may see a white screen or a generic error message.
The website encountered an unexpected error. Please try again later.
Solution: Run lando drush ws to display the latest error logs. it can help pinpoint where the error is.
Issue: When running lando rebuild -y, it rebuilds every service.
Solution: Most of the time, you only need to rebuild the app server and leave the other 7 services alone. Run lando rebuild -s appserver.
Instead of manually prefixing lando commands with winpty, you can use an alias to automatically do it for you:
- Create a file named .bashrc in your home directory (i.e. c:\Users<username>)
- Edit the file and add this line:
alias lando="winpty lando"
Now whenever you type lando it will automagically actually run winpty lando.
Issue: When starting Lando you get an error like:
error: (HTTP code 500) server error - container 2fdbaffa9df2d4474d7518727b2a1c1925a4af5929b0775a4075a0b96c543426 is not connected to the network lando_bridge_network
Solution: Run docker ps -a to see what the 2fdbaffa9 container is, then run docker rm 2fdbaffa9df2d4474d7518727b2a1c1925a4af5929b0775a4075a0b96c543426 to remove the container and try lando start again to see if it works now.
If it still doesn't work, then reset Docker to factory settings which will remove all of your containers. You'll need to share your drive again and adjust your container settings such as number of CPUs and allocated memory. You'll also have to login with Terminus again after rebuilding your containers.