Search results

Never mind... Proxmox was working fine! I got a idea and doublechecked the vmbr6-network (WAN) by creating new container and connected it to vmbr6 (WAN). There the testmachine was accessible from DMZ. So I examined everything in OPNSense and found a faulty setting. Now I remember what I did...

Hi everybody, I'm running Proxmox several years without any issue. The machine has 6 NICs. One of them is WAN and another one is LAN. This is the network layout ( [] = Device/Machine, () = Network): (Internet) <--> [WIFI-Router w/ Modem] <--> (DMZ) <--> [Proxmox: [WAN] <--> OPNSense <-->...

I believe I solved it now. /etc/ipset.conf: create pvenode hash:ip family inet hashsize 1024 maxelem 65536 bucketsize 12 initval 0xxxxxxxxx add pvenode 100.100.100.1 add pvenode 100.100.100.2 add pvenode 100.100.100.3 create office hash:ip family inet hashsize 1024 maxelem 65536 bucketsize 12...

Hi, I'm trying to achieve following: I want everything, what comes in with TCP protocol, will be natted to 10.10.100.1 except: - Source IP 100.100.100.1 to destination port 22, 8006 - Source IP 100.100.100.2 to destination port 22, 8006 - Source IP 100.100.100.3 to destination port 22, 8006 -...

Hi, just tried that. But still didn't help, unfortunately: root@server:~# hostnamectl status | grep 'Static hostname' Static hostname: server

Hi I have an issue with Plesk running as container. An Plesk-extension needs the hostname is properly set as FQDN. Let say I want name it 'server.domain.tld' (on my machine I of course use valid hostname). I did: hostnamectl set-hostname server.domain.tld root@server:~# hostnamectl status |...

Hi Dominik, thank you for your reply. In the meanwhile I was on holiday, thus the late reply. After I updated the node from 6.2-15 to 6.4-15 the backup works as a charm now. This means my settings were already fine. Best regards Floh

Hello, I have an issue with a node (all other nodes are fine). I have a backup job set up in datacenter which make backup of all containers. On one node I always get: "There is a max backup limit of 1 enforced by the target storage or the vzdump parameters. Either increase the limit or delete...

No, I have a dedicated machine as firewall (OPNsense) and Proxmox Backup Server is running as VM on my QNAP.

It’s always better to keep the port closed if possible. So better use VPN. I don’t use VPN in that case but I opened the port only for specific source IP addresses (so only addresses of my Nodes). All other Source IPs are blocked by Firewall. Maybe it will give you some idea. Best regards Floh

Thanx!

Do we only need TCP? Or UDP? Or both? Best regards Floh

All Nodes are on different locations (different cities). Firewall are set so only IP-Address of Nodes are allowed to access to its Port 22 and 8006. All requests from different IP addresses are blocked by FW.

Sure. floh@node03:~$ cat /etc/network/interfaces # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration manually, # please utilize the 'source' or 'source-directory'...

Ok, I fixed the RDRC update error. It seems that reinstalling with Proxmox installer didn't really clear the disk. I cleared the disk and reinstalled, then these errors are gone. But still cannot join the cluster: Jul 15 20:55:19 node03 systemd[1]: Stopping The Proxmox VE cluster filesystem...

Time is ok, doublechecked with date command. The RDRC update error already happens before I try to join, so its freshly installed. Manual SSH is possible (using pubkey).

Sure it shouldn't keep in that state that I have mixed version. I'll keep all nodes at same versions. Now I tried with new node with version 6.4 with the same result. Syslog of Cluster (Version 6.3-3): Jul 15 16:16:04 node01 pvedaemon[1090]: <root@pam> successful auth for user 'root@pam' Jul...

Hello Mira, that helped. Thank you very much, now I know about the file corosync.conf. I tried again but still stuck at waiting for quorum... :eek: In WebGUI on Cluster if I click on new node, I got: tls_process_server_certificate: certificate verify failed (596) :rolleyes: Maybe it just...

I know that documentation, but what should I use as parameter for the delete command since Node03 doesn't appear in pvecm nodes so I dunno which name it has. pvecm delnode ?????? Just try with pvecm delnode node03?

I think, I'll reinstall Node03 and retry, but I have to remove the Node03 from cluster before joining the new one. Node03 appears in WebGUI (with red cross symbol, because it's not working). But it doesn't appear in CLI: root@Node01:~# pvecm nodes Membership information ----------------------...