[GH-ISSUE #16] does not work with proxmox ve 6.0 #15

Closed
opened 2026-02-26 17:43:57 +03:00 by kerem · 8 comments
Owner

Originally created by @elurex on GitHub (Sep 3, 2019).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/16

root@cv4pve:~# cv4pve-autosnap --host=10.10.90.50 --username=root@pam --password=[PW] --vmid=800 status
================ EXCEPTION ================
System.Exception
Problem connection!
at Corsinvest.ProxmoxVE.Api.Extension.Shell.Utils.CommandOptionExtension.ClientTryLogin(CommandLineApplication command)
at Corsinvest.ProxmoxVE.Api.Extension.App.AutoSnap.ShellCommand.CreateApp(CommandLineApplication autosnapCmd)
at Corsinvest.ProxmoxVE.Api.Extension.App.AutoSnap.ShellCommand.<>c__DisplayClass7_1.b__1()
at McMaster.Extensions.CommandLineUtils.CommandLineApplicationExtensions.<>c__DisplayClass9_0.b__0()
at Corsinvest.ProxmoxVE.Api.Extension.Shell.Utils.ShellHelper.ExecuteConsoleApp(CommandLineApplication app, TextWriter std
Out, String[] args)

Originally created by @elurex on GitHub (Sep 3, 2019). Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/16 root@cv4pve:~# cv4pve-autosnap --host=10.10.90.50 --username=root@pam --password=[PW] --vmid=800 status ================ EXCEPTION ================ System.Exception Problem connection! at Corsinvest.ProxmoxVE.Api.Extension.Shell.Utils.CommandOptionExtension.ClientTryLogin(CommandLineApplication command) at Corsinvest.ProxmoxVE.Api.Extension.App.AutoSnap.ShellCommand.CreateApp(CommandLineApplication autosnapCmd) at Corsinvest.ProxmoxVE.Api.Extension.App.AutoSnap.ShellCommand.<>c__DisplayClass7_1.<CmdStatus>b__1() at McMaster.Extensions.CommandLineUtils.CommandLineApplicationExtensions.<>c__DisplayClass9_0.<OnExecute>b__0() at Corsinvest.ProxmoxVE.Api.Extension.Shell.Utils.ShellHelper.ExecuteConsoleApp(CommandLineApplication app, TextWriter std Out, String[] args)
kerem 2026-02-26 17:43:57 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@codesmaker commented on GitHub (Sep 3, 2019):

I get the same error message with v5.4-10

<!-- gh-comment-id:527413604 --> @codesmaker commented on GitHub (Sep 3, 2019): I get the same error message with v5.4-10
Author
Owner

@franklupo commented on GitHub (Sep 3, 2019):

Hi,
in the new version it has been fixed. In the coming days I should release it.

Best regards

<!-- gh-comment-id:527425541 --> @franklupo commented on GitHub (Sep 3, 2019): Hi, in the new version it has been fixed. In the coming days I should release it. Best regards
Author
Owner

@franklupo commented on GitHub (Sep 3, 2019):

New version released

<!-- gh-comment-id:527499133 --> @franklupo commented on GitHub (Sep 3, 2019): New version released
Author
Owner

@elurex commented on GitHub (Sep 4, 2019):

its fixed... thanks...

also for status command output... is it possible to have an option output in json?

<!-- gh-comment-id:527787612 --> @elurex commented on GitHub (Sep 4, 2019): its fixed... thanks... also for status command output... is it possible to have an option output in json?
Author
Owner

@franklupo commented on GitHub (Sep 4, 2019):

its fixed... thanks...

also for status command output... is it possible to have an option output in json?

Good idea

<!-- gh-comment-id:527796749 --> @franklupo commented on GitHub (Sep 4, 2019): > its fixed... thanks... > > also for status command output... is it possible to have an option output in json? Good idea
Author
Owner

@franklupo commented on GitHub (Sep 4, 2019):

Hi,
if I did so:

-o | --output Type output (default: text) Text, Json, JsonPretty
what do you say?

Bets regards

<!-- gh-comment-id:527802451 --> @franklupo commented on GitHub (Sep 4, 2019): Hi, if I did so: > -o | --output Type output (default: text) Text, Json, JsonPretty what do you say? Bets regards
Author
Owner

@elurex commented on GitHub (Sep 4, 2019):

Yes! it would be great

<!-- gh-comment-id:527818875 --> @elurex commented on GitHub (Sep 4, 2019): Yes! it would be great
Author
Owner

@franklupo commented on GitHub (Sep 5, 2019):

See new release 1,2.0

Best regards

<!-- gh-comment-id:528369791 --> @franklupo commented on GitHub (Sep 5, 2019): See new release 1,2.0 Best regards
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cv4pve-autosnap#15
No description provided.