The current CLI has a bug associated with the rollout of the new console. Until we can get a fix, you can work around the issue by modifying the .kinvey file in the root of your business logic, and changing the "host" parameter to "https://legacy.kinvey.com".
If you're trying to init a new BL project, you can add the host at that time by adding the --host flag:
```
kinvey --host https://legacy.kinvey.com init
```
m
mfboettcher
said
over 6 years ago
fix worked for me. Pls, inform us if the problem is fixed.
Gilles Haiat
said
over 6 years ago
Hello
I am getting this error when trying to deploy to kinvey servers from cli:
ERR: Unable to reach Kinvey Servers at https://legacy.kinvey.com
thecodevik1ng
The CLI has stopped working for me on multiple platforms. I have the newest version (0.3.3). I get the following error when trying to init or deploy
$ kinvey deploy
Traceback (most recent call last):
File "", line 140, in
File "F:\Webserver\kinvey-bl-cli\build\kinvey\out00-PYZ.pyz\lib.api", line 68,
in verifyVersion
File "F:\Webserver\kinvey-bl-cli\build\kinvey\out00-PYZ.pyz\requests.models",
line 651, in json
File "C:\Program Files\Python-27\lib\json\__init__.py", line 338, in loads
File "C:\Program Files\Python-27\lib\json\decoder.py", line 365, in decode
File "C:\Program Files\Python-27\lib\json\decoder.py", line 383, in raw_decode
ValueError: No JSON object could be decoded
This is totally broken. Have restarted on both platforms and the error remains the same.