PVE Manager Versionpve-manager 4.4-13
я понимаю, что дело связанное с сертификатом, как ее решить?
Диску скоро трындец, не?
Есть такое предчувствие.
Самоподписанный серт что ли?
Исошник какого размера льёшь? У меня почему-то некоторые dvd нормально не заливались, хоть и с дисками всё хорошо.
пробовал 100мб, 300, 4гб,все с ошибкой, хотя подчеркну шаблоны из инета льются в легкую. Еще момент, когда начинаешь лить образ в компа, он как бы начинает лица в процентах примерно 5%, затем соскакивает на 0%, заливается вновь, затем опять возвращается к 0% так несколько раз, затем ошибка
Proxmox error uploading an iso solution
root@vh1:/var/tmp# wget http://mirror.compevo.com/proxmox/proxmox-ve_5.2-1.iso
—2018-08-30 16:27:37— http://mirror.compevo.com/proxmox/proxmox-ve_5.2-1.iso
Resolving mirror.compevo.com (mirror.compevo.com). 103.25.61.44
Connecting to mirror.compevo.com (mirror.compevo.com)|103.25.61.44|:80. connected.
HTTP request sent, awaiting response. 200 OK
Length: 641517568 (612M) [application/octet-stream]
Saving to: ‘proxmox-ve_5.2-1.iso’
2018-08-30 16:28:22 (10.9 MB/s) — Connection closed at byte 517359784. Retrying.
—2018-08-30 16:28:23— (try: 2) http://mirror.compevo.com/proxmox/proxmox-ve_5.2-1.iso
Connecting to mirror.compevo.com (mirror.compevo.com)|103.25.61.44|:80. connected.
HTTP request sent, awaiting response. 206 Partial Content
Length: 641517568 (612M), 124157784 (118M) remaining [application/octet-stream]
Saving to: ‘proxmox-ve_5.2-1.iso’
var/tmp is out of space the same as tmpfs
#this normally happens when Proxmox first uploads it to a place in /tmp on your / filesystem and if you have used a small HDD for testing it’s easy for a simple ISO upload to fail for this reason. You’ll have to wget directly to the main filesystem or datastore with more space.
Решение ошибки Proxmox VE — error 0 occurred while receiving the document
В Proxmox VE при добавлении ISO-образа через web-интерфейс возникает ошибка — error 0 occurred while receiving the document.
Рисунок 1 — Ошибка error 0 occurred while receiving the document
Решение
Нам необходим любой SFTP-клиент (WinCsp или FileZilla) для подключения к нашему Proxmox-серверу.
Выкладываем необходимый ISO-образ на заранее смонтированный диск или в саму систему по стандартному пути /var/lib/vz/template/iso, куда ранее пытались загрузить образ через web-интерфейс.
Проверяем добавленный образ через web-интерфейс:
Рисунок 2 — ISO-образ, доступный через web-интерфейс
Теперь с образом можно работать.
Нужна помощь? Администрирование Proxmox мы осуществляем в рамках услуги Администрирование серверов.
Proxmox 5.3.9 can't upload iso
I’m new to proxmox, I’ve actually installed my proxmox. After accessing to the webUI I tried to upload iso.
(Datacenter > node > local ( storage )).
Then I went into content > Upload then I tried to upload file.
Sadly It won’t upload anything. After reinstalling it nothing had changed.
The strangest things is that I installed the proxmox is installed to another server and it is actually working well.
I know there is a solution is using scp to upload file, but if the protocol is forbidden in my company, I can’t upload it.
The disk space is free:
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/md1 20G 1,9G 17G 11% /
Proxmox Staff Member
- Feb 7, 2019
- #2
Best regards,
Mira
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
eholo
New Member
- Feb 7, 2019
- #3
eholo
New Member
- Feb 7, 2019
- #4
dcsapak
Proxmox Staff Member
- Feb 8, 2019
- #5
Best regards,
Dominik
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
eholo
New Member
- Feb 8, 2019
- #6
I did check the syslog, and nothing seems to be appeared at this time. Do you know if proxmox use PHP and what is their path, or have web log like apache or nginx ?
I also try to empry my web cache to be sure that’s not something in the cache. I also tried different web navigator ( Chrome, Firefox and IE ).
eholo
New Member
- Feb 8, 2019
- #7
I did try a new upload, here is the following error from the syslog:
Feb 8 08:44:45 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:46 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:46 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:47 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:48 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:48 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:49 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:49 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:50 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:51 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:51 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:52 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:54 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:54 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:55 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:55 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:56 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:56 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:57 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:57 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:58 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:44:59 proxmox-01 pveproxy[1027]: problem with client 147.98.1.13; ssl3_read_bytes: sslv3 alert bad certificate
Feb 8 08:45:00 proxmox-01 systemd[1]: Starting Proxmox VE replication runner.
Feb 8 08:45:01 proxmox-01 CRON[1458]: (root) CMD (/usr/local/rtm/bin/rtm 50 > /dev/null 2> /dev/null)
Feb 8 08:45:01 proxmox-01 systemd[1]: Started Proxmox VE replication runner.