Search results

  1. J

    tty console not working after upgrade

    PVE 8.2.7 I ran do-release-upgrade on a ubuntu 22.04 container to upgrade it to 24.04 and now the console no longer works. The container boots and runs fine but the console window in the Proxmox web UI is just blank. Pressing enter does not do anything. I can not type any characters. Been...
  2. J

    Feature Request: Do not have a default value for Target Node on VM migration

    Do not have a default value for Target Node on VM migration. It's way too easy to forget to select a node and end up migrating to the wrong host. Maybe I'm just old and forgetful and should pay closer attention, but I will be interested to see if this gets any attention from the community. Side...
  3. J

    Adding a cluster node with Shared LVM/iSCSI and multipath

    What is the proper set of steps to add a new node to a cluster when using shared LVM over iSCSI and multipath? I have had mixed results with this. I've been migrating my servers from ESXi to Promox one at a time. Adding the first 2 nodes to the initial Proxmox host cluster went fine, But the...
  4. J

    [SOLVED] LXC Netmask strangeness

    In the container config file I have net0: name=eth0,bridge=vmbr0,firewall=0,gw=192.168.99.1,hwaddr=56:C9:75:FB:4E:8F,ip=192.168.99.40/24,type=veth But in the container, I get root@pihole:~# ip addr show dev eth0 43: eth0@if44: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP...
  5. J

    Default config template breaks PostgreSQL

    Version: 5.2-2 in /var/lib/pmg/templates/postgresql.conf.in there are two timezone related parameters (timezone and log_timezone) with the default value of 'localtime'. When running without modification the PostgreSQL service fails to start. 2019-05-14 20:21:08.941 GMT [745] LOG: invalid...
  6. J

    DNSBL is not working as well as expected

    I have DNSBL Sites set to b.barracudacentral.org,zen.spamhaus.org with DNSBL Threshold set to 1. Yet we continue to get spam from IP addresses that, according to mxtoolbox.com are on one or both of those lists. We are seeing a lot of spammers out there now that have legitimate DKIM and SPF, so...
  7. J

    Greylisting and order of operations

    We currently use greylisting because it (appears to) stop a lot of bogus messages. But our users get a little annoyed with the delay from some poorly configured senders plus I get a little tired of trying to explain it. In looking at the Greylist tab in the Tracking Center page, I see an...
  8. J

    Multiple DNS Servers for OpenVZ guests

    It would be nice if the Proxmox Web UI (v2.2) had better (more intuitive?) support for configuring a container with multiple DNS servers. I eventually found out via trial and error that you can enter multiple IP addresses in the "DNS server" field in the web UI. There is nothing in the web UI...
  9. J

    Avoid duplicate disclaimers

    Anyone have any suggestions for avoiding repeated insertion of a disclaimer when a number of replies go back and forth?
  10. J

    Virus blocked only after outbound forwarding attempt

    We have a couple of addresses that get forwarded (by our back-end mail system) to addresses outside of our domain. We occasionally get notifications from proxmox that it blocked an outbound virus going to that forwarded external address. So it appears that the message gets past the inbound virus...
  11. J

    Hide Internal Headers - Feature Request

    I was looking at the headers in a message sent from our domain to the outside world and noticed that all the host names and private IP addresses of all the internal systems through which the message passed were visible. A quick search yielded this...
  12. J

    Can't backup to Win 2008 Share

    We replaced our file server with Win 2008 x64. Now proxmox scheduled backups are failing. Windows share permissions are the same. Just changed the hostname in the proxmox backup configuration. From other Windows machines, I can read/write on the share using the same account that I am providing...
  13. J

    Feature Request: New Action: Reject 450/550

    Our implementation of recipient verification is working nicely with one exception. Certain mail aliases are intended for internal use only, yet they successfully pass receiver verification because they are deliverable on the back-end mail servers. So we created a Who list and a Block/Notify...
  14. J

    Statistics with Verify Receivers On

    One last (I hope) question about recipient verification... It appears that rejects due to failed recipient verification are not counted anywhere in the statistics. Is that correct? I understand that no mail content is transmitted when a recipient verification fails, but the process still...
  15. J

    Order of Receiver Verify/Greylist

    From reading the forums, I understand that receiver verification comes before greylisting, but I don't understand the reason for this choice. We used to maintain lists of valid addresses in Proxmox and block all others instead of using receiver verification. This limited virtually all...
  16. J

    User self-service whitelists/blacklists

    We use greylisting, so our users have come to learn that sometimes it's best to whitelist a new contact to avoid the first-time delays. However, as administrators, we are growing somewhat tired of manually adding whitelist entries on behalf of our users. The web interface link in the daily spam...
  17. J

    SPF Options?

    We have recently been getting complaints from internal users that legitimate messages to them from outside are being rejected. When we search the proxmox logs, we often find it's an SPF issue on the sender's side. I like the idea of SPF and if people are going to configure their domain for it...
  18. J

    Extra junk in subject on Daily Spam Report

    Not a big deal, but I'm wondering why this is happening. Some, but not all, daily spam reports are coming through with some character set information embedded in the subject. See header excerpt below. Any ideas why? Content-Type: multipart/related...
  19. J

    Information about outgoing bounces?

    We recently reconfigured our network to pipe all outgoing messages through proxmox. The daily status report tells me how many outgoing mails bounced, but nothing else. I had become accustomed to receiving a handful of bounce messages directed to postmaster@mydomain.com, but now I get nothing...