Hello,
Iām just stuck in Github codespaces, even after I read many tutorials.
Firstly, the site github.dev shows 2 kind of consoles (1 bash and 1 named Codespaces: viktor-cli). I suppose to operate in the latter; the first thing is that viktor-cli is not available but I must call ~/.viktor/viktor-cli or create an alias.
Is the play button in web version of visual studio code supposed to work? AFAIK, it does not have to be used - I kindly ask a confirmation on this.
Anyway, I used the following commands:
- ~/.viktor/viktor-cli create-app --app-type editor
- ~/.viktor/viktor-cli clear
- ~/.viktor/viktor-cli install
- ~/.viktor/viktor-cli start
The last one gives me the error:
App registered_name
is invalid. Make sure to provide a valid registered_name
in the viktor.config.toml
file.
I edited the toml file by uncommenting the line āregistered_name = ā¦ā and saved the file, but nothing changes when trying to re-run the app.
In addition, the command ā~/.viktor/viktor-cli configureā returns me the error: āERROR:
Exiting because of an error: the provided email address and token are not registered at VIKTOR. Please rerun the āconfigureā command with valid credentialsā
but Iām sure credentials are correct.
I think Iām missing something important in configuring and/or using Viktor, can some one help? thanks in advance
Hi johnnyontheweb,
Welcome to our community forum!
Unfortunately, there was a regression in the platform today which caused this error to appear in a certain case. It would only appear if you had (re-)installed your app this afternoon after the newest connector release (v5.29.0). Weāve already rolled-out a fix for this, so the error should not appear anymore.
Our apologies for the confusion. Hopefully this solves your problem.
We will also look into why the viktor-cli
is only available through the full path (~/.viktor/viktor-cli
) and not using the shortcut.
Kind regards,
Hi kvangiessen,
thanks for your prompt reply. Shortcut for viktor-cli now works. I cleared and installed the app, and set the registered_name equal to the name of the workspace, but I still get the following error when I start it:
`2024-11-05 07:25:22.235 INFO : VIKTOR connector v5.29.0
2024-11-05 07:25:22.235 INFO : VIKTOR SDK v14.16.2
2024-11-05 07:25:22.364 ERROR : Could not connect to the VIKTOR platform: Malformed connection (code:500, body:
Server Error (500)
Server Error (500)
`
In addition, the āviktor-cli configureā returned the same error as before: Exiting because of an error: the provided email address and token are not registered at VIKTOR. Please rerun the 'configure' command with valid credentials
I have a reset to set-up the initial workspace and the same error 500 appears also in local installation on my Windows machine
Hi johnnyontheweb,
That is unfortunate, it seems that somewhere along the line something went wrong when saving your Developer account token.
Could you please retry the activation flow? You can reset your Developer account by:
- within the VIKTOR platform, click your profile icon in the top right
- click Settings
- on the new page, select āDeveloper Accountā (side bar)
- then at the bottom of the page, click āReset Developer Accountā
This should guide you through the activation flow once again, and will also reset your token.
Hello,
I did it (2 times), but the same error appears (error 500, malformed connection) on app start. However, it seems it does not depends on me, since it is the server to reply with:
<!doctype html>
<html lang="en">
<head>
<title>Server Error (500)</title>
</head>
<body>
<h1>Server Error (500)</h1><p></p>
</body>
</html>
I can say that connectivity is ok, since I can successfully ping cloud.viktor.ai.
ps.
when I perform the activation of a local installation, is the token visible? or it is stored automatically on machine? in other words: when I run viktor-cli configure, may I have to always confirm the existing token?
Hello johnyontheweb,
The 500 status code seems to indicate something is wrong on our side. Weāve spotted some internal errors in our alarms and rolled out a fix for those, this fix will most likely fix your problem as well. Please try the start
command once more.
In any case, if it still doesnāt work, would you be able to post the following data:
- VIKTOR connector version (will be printed when you attempt to start the app)
- VIKTOR cli version (printed when running
viktor-cli version
)
Wrt the token, you can actually rotate the token yourself, so you could re-run the configure
command and when it prompts for a token you can obtain this from the same settings page as above (click the āGenerate new tokenā button)
Kind regards,
Thanks, itās working now!
1 Like