Search results

Well, it is INTEL-NUC. 'Clearlinux' is also 'Intel' product... So seems that both should be compatible...

What could be problem? I'm trying to install newest release 'Clearlinus', but stop with errors when started... kvm: warning: host doesn't support requested feature: CPUID.07H:EDX.ssbd [bit 31] kvm: Host doesn't support requested features TASK ERROR: start failed: QEMU exited with code 1

Yes, still the same problem...

Some update (sorry forgot to mention that; just now realized) the 'ssh' start session problem I have when trying from 'Windows10'. From any 'Linux' it works.

# nc 192.168.1.1.5 22 SSH-2.0-OpenSSH_7.9p1 Debian-10+deb10u2

Followed that, then: root@proxmox:~# service sshd restart But still: C:\>ssh root@192.168.1.5 ssh: connect to host 192.168.1.5 port 22: Connection refused Port '22' is open. Oct 14 16:36:09 proxmox systemd[1]: Started OpenBSD Secure Shell server. Oct 14 16:36:09 proxmox sshd[7646]: Server...

Yes, I have access to GUI via https://192.168.1.5:8006. See the result: root@proxmox:~# ss -a -4 | grep ssh tcp LISTEN 0 128 0.0.0.0:ssh 0.0.0.0:* root@proxmox:~#

Yes, the firewall is 'ON', but none rule is defined... I've never touched it... Should I define 'allowed' 'all traffic' for port '22'...?

How can I access 'proxmox' console from another PC via ssh? I'm trying some advice - but looks like this is not working... Something must be enabled on 'proxmox' ? C:\>ssh root@192.168.1.5 ssh: connect to host 192.168.1.5 port 22: Connection refused

O.K. This helped... Looks like some earlier update was broken due to poor Internet band/connection...

pveversion -v is showing following: root@proxmox:/# pveversion -v proxmox-ve: not correctly installed (running kernel: 5.0.15-1-pve) pve-manager: 6.2-12 (running version: 6.2-12/b287dd27) pve-kernel-helper: 6.2-7 pve-kernel-5.0: 6.0-5 pve-kernel-5.0.15-1-pve: 5.0.15-1 ceph-fuse...

Thank you, but still the same problem... After this operation, 784 MB of additional disk space will be used. Do you want to continue? [Y/n] y Err:1 http://fr.cdn.proxmox.com/debian/pve buster/pve-no-subscription amd64 lvm2 amd64 2.03.02-pve4 Connection failed [IP: 51.91.38.34 80] Err:2...

I could not find the problem. Is the 'proxmox' update server down now...? I can not ping to 212.224.123.70. (download.proxmox.com). On the other hand ping to other IP/server 212.224.123.7 works. Any idea what could be wrong? Any other server for 'proxmox' updates...? E: Failed to fetch...

O.K. Thx... I must look into this issue...

Partly good… Why some connections fail? Proxmox servers are down? E: Failed to fetch http://download.proxmox.com/debian/pve/dists/buster/pve-no-subscription/binary-amd64/lvm2_2.03.02-pve4_amd64.deb Connection failed [IP: 144.217.225.162 80] E: Failed to fetch...

When changed all to 'https'; result as below... root@proxmox:/# apt-get update && apt-get dist-upgrade Ign:1 https://ftp.debian.org/debian buster InRelease Ign:2 https://download.proxmox.com/debian/pve buster InRelease Err:3...

Strange... Nothing is blocked by Internet provider... So as temporary solution change 'http' to 'https' ? Will that work...?

Yes, indeed... Looks like this is working... Any solution for that? root@proxmox:~# wget --no-check-certificate https://ftp.pl.debian.org/debian/pool/main/i/icu/libicu-dev_63.1-6+deb10u1_arm64.deb --2020-09-29 19:20:58--...

Well... Still something not O.K. root@proxmox:~# wget http://ftp.pl.debian.org/debian/pool/main/i/icu/libicu-dev_63.1-6+deb10u1_arm64.deb --2020-09-29 18:58:29-- http://ftp.pl.debian.org/debian/pool/main/i/icu/libicu-dev_63.1-6+deb10u1_arm64.deb Resolving ftp.pl.debian.org...

O.K. Changed, but still stop at the same point: Get:10 http://ftp.pl.debian.org/debian buster/main amd64 libicu63 amd64 63.1-6+deb10u1 [8,300 kB] Get:10 http://ftp.pl.debian.org/debian buster/main amd64 libicu63 amd64 63.1-6+deb10u1 [8,300 kB] Get:10 http://ftp.pl.debian.org/debian buster/main...