Here are some errors and issues you may encounter when using VIP CLI.
In order to maintain the integrity of your sites and various services it requires, commands that utilize excessive CPU, memory, or I/O may be terminated. See the WP-CLI Best Practices section for ways to monitor for and avoid this scenario.
There is also a limitation on the number of commands that can be run concurrently. Production environments are limited to a maximum of four concurrent commands and non-production environments are limited to two.
Applications missing from
vip app list
For you to access an application via VIP-CLI, you must have at least
read access to the GitHub repository for that application. If you do not see all the applications you expect when running
vip app list, please follow this procedure:
- Check you have
readaccess to the GitHub repository for the application(s) you expect to see. If you do not have access to these repositories on GitHub then you should contact someone on your team who has admin rights or alternatively contact VIP support.
- If you do have
readaccess to the application repository on GitHub, but you do not see the application listed via
vip app listthen…
vipand follow the prompts to log in.
vip app list. If you are still not seeing all the applications you expect then please get in touch with VIP support.
Note that to run some WP-CLI commands, you’ll need
write access to the GitHub repository.
“Status code 401”
You may receive an error including the line
Received status code 401, for example:
Failed to fetch apps: Error: Network error: Response not successful: Received status code 401
Please try the following:
vipand follow the prompts to log in again.
“The command is not permitted at this time”
In certain cases, we block some core and other commands for security, performance, and other reasons. To see a full list of the commands which are available to you, you can use
Error: Rate limit exceeded: Please wait a moment and try again.
We use rate-limiting to reduce API-abuse and charge our APIs. If you are seeing this error, it usually means you’re sending too many requests to our servers either from the VIP Dashboard, VIP CLI, or both. Given both VIP Dashboard and VIP CLI use the VIP API under the hood, this means that requests from both counts toward the rate limits.
Here are some solutions to try if you see such errors:
- Close any non-used VIP Dashboard or VIP CLI windows
- Reduce the number of concurrent commands you run using VIP CLI
- In some cases, a VIP CLI command isn’t stopped correctly (especially if the command was killed using Control ^ + C, or equivalent). In that case, some remaining processes may be still running in the background. To stop these processes, please quit the command line window completely.
These rate limit errors are between the end-user and our APIs. This means that these errors are only appearing in the VIP CLI window and aren’t affecting the original output or logs of the command. Even if you see these errors, the command is running fine behind the scenes.
This error is received when the command is cancelled either by you or automatically by our systems for exceeding resource limits.
“Connection lost, retrying…”
If your internet connection drops while running a command, we’ll keep trying to reconnect in the background. During this process, you may get a “Connection lost, retrying…” message logged to your console. If we can’t make a connection in the span of 1 minute, we’ll stop trying and you’ll be disconnected from the command.
“Maximum running command count has been reached for the site”
This indicates that there aren’t enough available resources to run the commands or you’ve currently exceeded the maximum number of concurrent commands that can be run. You can use the VIP Dashboard to view (and cancel) running commands.
By default, 2 concurrent CLI commands can be run on non-production sites, and 4 concurrent CLI commands can be run on production sites.
“Error during Handshake”
This typically is due to cases where
stdin input is being manipulated through a shell utility such as
xargs. See the “Looping” section under “Advanced Usage” for more details.