Hi there,
Been attempting to troubleshoot for the past hour upgrading from 0.4 to 1.0 to 1.1.
I noticed 1.1 was just updated 9 hours ago and wonder if this error may be related to that, however, I was attempting to rebase and cannot enable an environment.
This error comes up…
[ERROR]: error creating service client (client version error accessing api endpoint 'https://api-v1.zrok.io': [POST /clientVersionCheck][400] clientVersionCheckBadRequest expecting a zrok client version matching 'v1.0' version, received: 'v1.1.0 [e51df0aa]'; please visit ' Install | zrok ' for the latest release!)
Edit: I’ve already released the environments on the UI, but still can’t enable.
Edit 2: Currently also using the start.server from dovholuknf’s bootstrapper if that helps.
If someone could point me in the right direction would be appreciated. I got a game to run in 2 days and it would be a pain to not be able to use zrok servers.
Thanks
Hi @SyndicateZulu, welcome to the community. It seems pretty clear from that error that there's a mismatch of versions. I think you should downgrade to v1.0 based on that error. Did you update to zrok 1.1 after 1.0 couldn't enable the environment?
Also out of curiosity, why are you enabling the environment again? Something else must have gone wrong to make you have to do that?
Hey there Clint!
Thanks for the warm welcome. So seeing the v1.1.1 today, after downloading, has allowed me to enable my environment. However, upon using the script
powershell.exe -ExecutionPolicy Bypass -File start-server.ps1 -Public
I’ve run into this error.
The argument 'start-server.ps1' to the -File parameter does not exist. Provide the path to an existing '.ps1' file as an argument to the -File parameter.
As a response to your final question, I was enabling the environment because I had that version mismatch error when I decided to upgrade from v.4 to v1.1.0. I then decided to hard reset my environment assuming that was the mismatch.
Glad to hear you were able to enable the environment.
I assume you are running this?:
powershell.exe -ExecutionPolicy Bypass -File start-server.ps1 -Public
Make sure you're in the directory containing 'start-server.ps1'. I would guess you're not in that folder.
Update from v1.1.0 to v1.1.1. This will correct any versioning issues.
Yeah sorry that was my goof. Got it routing properly now.
V1.1.1 is working smoothly as well. Thank you fellas.
2 Likes