ISPCONFIG3 mail all of a sudden doesn't work and ispconfig_update.sh --force won't work

Discussion in 'Installation/Configuration' started by vestport, Dec 7, 2025 at 11:37 PM.

  1. vestport

    vestport Member

    Gets the error "Unable to retrieve version file."

    Any tips on how I can get the files back so I can force update? I may have done and "apt update" that blew away the files not sure. Mail accounts are there but can't send or receive mail and can't update with missing files. Websites work fine.

    Thanks in advance for any replies
     
    vestport, Dec 7, 2025 at 11:37 PM
    #1
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The error message means your system is not able to fetch the version file from ispconfig.org. So you seem to have an internet connection issue, which may also be the reason why your emails are not working.

    Manual ISPConfig update instructions, copied from release notes:

    Code:
    cd /tmp
wget https://www.ispconfig.org/downloads/ISPConfig-3.3.0p3.tar.gz
tar xvfz ISPConfig-3.3.0p3.tar.gz
cd ispconfig3_install/install
php -q update.php
     
    till, Dec 8, 2025 at 12:25 AM
    #2
    vestport and ahrasis like this.
  3. vestport

    vestport Member

    Thanks Till! I'll try that now. This was a migration so that is why I don't have the files. Not sure what happened that mail all of a sudden did not work. I'll report back in a bit so hopefully helps someone else.

    I just tried and won't work because there are also dns issues. Oh man! when I ping yahoo I get this:

    root@ns1:~# ping www.yahoo.com
    ping: www.yahoo.com: Temporary failure in name resolution

    I just checked and my /etc/resolv.conf file somehow got screwed up. Rebooting now and will follow up. Again, not sure how this all happened.

    Not sure how all this happened. Very strange.

    My gateway and everything is correct when I look at /etc/network/interfaces. Not sure what the heck is going on.

    Somehow my /etc/resolv.conf keeps getting overwritten after reboot to:

    nameserver 127.0.0.53
    options edns0 trust-ad
    search DOMAINS

    I put a "#" in front of "nameserver" (#nameserver 127.0.0.53 and below put my real nameserver in and it keeps resetting on reboot.

    Not sure what to do or how this happened. Still trying to get to the bottom of the dns issues so I can try what Till suggested.


    I did a

    root@ns1:~# systemctl disable --now systemd-resolved.service
    rm /etc/resolv.conf
    Removed "/etc/systemd/system/sysinit.target.wants/systemd-resolved.service".
    Removed "/etc/systemd/system/dbus-org.freedesktop.resolve1.service".

    rebooting to see if anything is still creating /etc/resolv.conf. If not I will create a new one and hopefully everything will be back to normal.
     
    Last edited: Dec 8, 2025 at 2:13 PM
    vestport, Dec 8, 2025 at 1:33 PM
    #3
  4. remkoh

    remkoh Well-Known Member HowtoForge Supporter

    So you don't have internet connection issues but dns resolving issues on your server.
    Fix that and all should be fine again.
     
    remkoh, Dec 8, 2025 at 1:49 PM
    #4
  5. vestport

    vestport Member

    Yes, I tried the above and even deleted the symbolic link to the /etc/resolv.conf and rebuilt a new /etc/resolv.conf. It is still being overwritten.
     
    vestport, Dec 8, 2025 at 2:23 PM
    #5
  6. remkoh

    remkoh Well-Known Member HowtoForge Supporter

    Is it a Proxmox VM by any chance?
    The hint will be: ifupdown2
     
    remkoh, Dec 8, 2025 at 2:34 PM
    #6
  7. vestport

    vestport Member

    Tried

    sudo chattr -i /etc/resolv.conf

    but gives the following error

    chattr: Operation not permitted while setting flags on /etc/resolv.conf
     
    vestport, Dec 8, 2025 at 2:38 PM
    #7
  8. vestport

    vestport Member

    ? not sure what aProxmox VM is? This was an ispconfig3 migration from apache server to apache server. Full servers setup no VMware if that is what you mean.
     
    vestport, Dec 8, 2025 at 2:39 PM
    #8
  9. vestport

    vestport Member

    Dammit, I was so mixed up I forgot to su to use the dang command! Duh!!!! Lets see what happens now. Works now prior to reboot so let's see if it gets overwritten. Report back in a sec. Appears to be working now! Okay, time to try Till's suggestion for mail.
     
    Last edited: Dec 8, 2025 at 2:47 PM
    vestport, Dec 8, 2025 at 2:41 PM
    #9
    ahrasis likes this.
  10. remkoh

    remkoh Well-Known Member HowtoForge Supporter

    So you're saying that the migration tool was overwriting the resolver settings according to you?
    I find that very hard to believe. The migration tool is for migrating data only (websites, mail etc) and not basic system settings as far as I know. Though @till will know for sure.
     
    remkoh, Dec 8, 2025 at 2:58 PM
    #10
    till likes this.
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    This whole issue is not related to the migration you did, nor to the Migration Tool. The Migration Tool does not alter your network and DNS resolving setup at all. If the resolv.conf is changed on reboot, then it's done by your hoster (e.g. maybe by DHCP or other ways) or a VM management software like Proxnox when it's a container. This whole topic is not an ISPConfig related as neither ISPConfig nor the Migration Tool are doing the changes in that file.
     
    till, Dec 8, 2025 at 3:08 PM
    #11
    remkoh likes this.

Share This Page