Recent content by Kordian

Hello, I had this issue already when upgrading from 8 to 9. Now it is there again. When I try accessing the GUI I get these errors: Uncaught SyntaxError: missing } after property list proxmoxlib.js:750:2note: { opened at line 42, column 29proxmoxlib.js:42:29 Uncaught TypeError: can't access...

Thank you for the help. In my case I think it was the problem how proxmox and the storage communicate and cooperate. But using parted solved the issue and now I can freely expand the resources.

Thank you, will test.

Thank you. So if I do not create any label nor "partition" on FC SAN, this should then go without problems?

Hello, I have a proxmox cluster and a shared FC LUN. I am trying to extend currently used storage, following this: Rescan should be done on ALL nodes: pvs -o +tags multipath -ll LUN_name echo 1 >/sys/block/sdX/device/rescan echo 1 >/sys/block/sdY/device/rescan echo 1...

What does this have to do with the problem, or the fact that the upgrade does not upgrade a critical component? If you have nothing to do, keep on doing nothing, instead of posting useless comments. Thank you in advance.

Yes, I read it. No word of ifupdown problems afterwards. Actually before the upgrades I added the hwaddress to the config, as suggested. Still it all went wrong!

Well, since I am after 6 hours of fighting with getting my production system working, first of all many thanks to the whole Proxmox team for screwing the upgrade process up and not informing users of it! I hope karma will thank you better than I can. The story: 2 days ago I decided to upgrade my...

Hello, I am unable to upgrade my Proxmox 6.4 - get numerous Err:6 http://download.proxmox.com/debian/pve buster/pve-no-subscription amd64 libquorum5 amd64 3.1.5-pve2~bpo10+1 403 Forbidden [IP: 212.224.123.70 80] I can access these resources through the browser without problems. curl...

OK, solved it myself. You need to configure the proftpd to limit the passive ports, and then enable them on firewall. Or has anybody any other idea?

Yes, running ss -tunlp shows the proftpd port 21 listening. Running nmap returns: Starting Nmap 7.70 ( https://nmap.org ) at 2020-10-28 18:47 CET Nmap scan report for xxx.xxx.xxx.xxx Host is up (0.00024s latency). PORT STATE SERVICE 21/tcp open ftp MAC Address: XXX (Unknown) This works fine...

Of course I have rules set, including tcp 21 port enabled.

No help? No ideas? Is uefi working with proxmox at all?

No help? No ideas?

I know that. As long as I define the firewall and enable it on the datacenter and container, ftp is working. When I enable it on the vm, the traffic is blocked. Partially, as logon gets through.