[SOLVED] Error Internal Server Error (500) failed to scan remote - if you write the address in the format IPv6 2001:xxxxx

[Maksel]

I have a task. Configure synchronization between servers via only IPv6.
if you write an address in XX:.....:XX format, it gives an error when a synchronization task is submitted.

If you add an entry to the /etc/hosts file

echo "2001:.....:199  myprimarypbs" >> /etc/hosts

error - no

Server:
proxmox-backup-server 1.0.11-1 running version: 1.0.11
Client:

proxmox-backup-client version
client version: 1.0.12

 

[dcsapak]

the error is displayed in the dropdown box:
'invalid authority' so i guess that you did not enter the fingerprint for the host, so it tries to validate the ssl certificate and that fails

 

[Maksel]

the error is displayed in the dropdown box:
'invalid authority' so i guess that you did not enter the fingerprint for the host, so it tries to validate the ssl certificate and that fails

No, no, if there is an error in the fingerprint, there will be such an error

Internal Server Error (500)
failed to scan remote 'pbs1-kv-hostname' - remote connection to 'myprimarypbs' failed - error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1915:

My fingerprint is correct.
The error was when using the IPv6 address

root@pv2:/etc/proxmox-backup# cat remote.cfg
remote: pbs1-kv-hostname
    auth-id pr8920@pbs
    comment copy from the first server
    fingerprint 35:.........................:c5
    host myprimarypbs
    password c......................m

remote: psb1-kv-ipv6
    auth-id pr8920@pbs
    comment copy from the first server
    fingerprint 35:.........................:c5
    host 2001:xxxxxxxxx:199
    password c......................m

tcpdump -n -p -i vmbr0 host 2001:xxxxxxxxx:199

tcpdump does not output anything, i.e. the traffic doesn't even go to the remote server.
error when using ipv6 address


If using cli

root@pv2:/etc/proxmox-backup# proxmox-backup-manager sync-job list
┌─────────────────┬───────┬──────────────────┬──────────────┬──────────┬─────────┐
│ id              │ store │ remote           │ remote-store │ schedule │ comment │
╞═════════════════╪═══════╪══════════════════╪══════════════╪══════════╪═════════╡
│ s-4d8056b9-472b │ sdc   │ pbs1-kv-hostname │ sdd          │ 3:10     │         │
└─────────────────┴───────┴──────────────────┴──────────────┴──────────┴─────────┘

root@pv2:/etc/proxmox-backup# proxmox-backup-manager sync-job create task2 --remote psb1-kv-ipv6 --remote-store sdd --store sdc

root@pv2:/etc/proxmox-backup# proxmox-backup-manager sync-job list
┌─────────────────┬───────┬──────────────────┬──────────────┬──────────┬─────────┐
│ id              │ store │ remote           │ remote-store │ schedule │ comment │
╞═════════════════╪═══════╪══════════════════╪══════════════╪══════════╪═════════╡
│ s-4d8056b9-472b │ sdc   │ pbs1-kv-hostname │ sdd          │ 3:10     │         │
├─────────────────┼───────┼──────────────────┼──────────────┼──────────┼─────────┤
│ task2           │ sdc   │ psb1-kv-ipv6     │ sdd          │          │         │
└─────────────────┴───────┴──────────────────┴──────────────┴──────────┴─────────┘

I add tasks via the CLI.
And then execute it via the Web - then it gives an error, and the traffic is zero.

2021-04-06T14:48:33+03:00: TASK ERROR: remote connection to '2001:хххххх:199' failed - invalid authority

 

[dcsapak]

ok, you're right, we do not handle ipv6 literal addresses correctly

i sent a patch to the devel list: https://lists.proxmox.com/pipermail/pbs-devel/2021-April/002669.html

for now, you'd have to put the ip in /etc/hosts and use hostnames

 

[Maksel]

ok, you're right, we do not handle ipv6 literal addresses correctly

i sent a patch to the devel list: https://lists.proxmox.com/pipermail/pbs-devel/2021-April/002669.html

for now, you'd have to put the ip in /etc/hosts and use hostnames

dcsapak, hi. i upgraded to 1.1-5​

nothing has been fixed. patch - did not apply?

 

[dcsapak]

nothing has been fixed. patch - did not apply?

no, nobody applied the patch, i pinged it now, so hopefully somebody will look at it

 

[Maksel]

Thank you. The problem was solved in version (1.1.7-1) unstable

client/http_client: add necessary brackets for ipv6

just updated to (1.1.8-1) stable - everything works.

 

[termizi]

Mine upgraded to v1.1.13, yet no luck / success.

Any idea?

 

[dcsapak]

Mine upgraded to v1.1.13, yet no luck / success.

Any idea?

what exactly did you enter, and which error message do you get? the problem of op should be fixed

 

[termizi]

what exactly did you enter, and which error message do you get? the problem of op should be fixed

Thanks dcsapak!

My earlier CLI attampts were prompted with errors as follows;

<message were snipped>
:
:
Need to get 0 B/194 kB of archives.
After this operation, 1024 B disk space will be freed.
Setting up systemd (244.1-3) ...
Detected unsafe path transition /var → /var/log during canonicalization of /var/log/journal.
Detected unsafe path transition /var → /var/log during canonicalization of /var/log/journal.
Detected unsafe path transition /var → /var/log during canonicalization of /var/log/journal.
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error exit status 73
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Exiting from upgrade with status 100.

Resolution was;

It's already SOLVED as I manually run chown command via CLI;

#chown root:root / ( I do not know why and how the / ownership was changed other than root:root)
#apt upgrade (successfully ended with CC=0)