Should i upgrade to debian 13?

Discussion in 'Installation/Configuration' started by pecka33, Jan 25, 2026.

Thread Status:
Not open for further replies.
  1. pecka33

    pecka33 Member

    Hello,

    i am using debian 12 with latest version of ispconfig? Should i upgrade to debian 13 and if anwer is yes is here any safety manual?

    Thank you.
     
    pecka33, Jan 25, 2026
    #1
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    till, Jan 25, 2026
    #2
  3. /dev/null/

    /dev/null/ New Member

    /dev/null/, Jan 31, 2026
    #3
  4. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    :eek:
     
    ahrasis, Jan 31, 2026
    #4
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    @ahrasis The user /dev/null has been constantly posting misinformation here for a few days and hijacking other users threads. Using a cloud server (a virtualized server that supports scaling in a datacenter where multiple systems run on the same hardware) is no indication of which distribution flavor is being used.

    This is not the case. You know that your issue comes from installing a too minmal netinst setup, which did not even have the resolvconf command. So the solution for your problem is to either install resolvconf package or systemd-resolved before installing ISPConfig.

    /dev/null: You keep hijacking other threads on different topics in an attempt to try to gain some attention, even after being informed that updating and installation are two completely different things and after your initial issues were resolved, you posted yourself what you had to do to make it work on your specific setup. Also, I nowhere said that ISPConfig needs a cloud flavoured distribution. It just requires you to have a working standard name resolution configuration, which includes the resolvconf command.
     
    till, Jan 31, 2026
    #5
  6. /dev/null/

    /dev/null/ New Member

    misinformation is a bit harsh from you direction, but if you think that way, sorry;
    Using cloud server in a real datacenter indicates that image of that system was tempered to fit the datacenter system infrastructor in most optimal way, it no where near clean system, from small ajustments in network configuration to installing external packages as so as using proxy between system and repo. But still yeah, its not indicator of anything, which is not the point in my issues reports.

    I know how we do our labs or hosting, not everyone does 3-2-1, some just apt upgrade all the way just to find out that something broke.
    I just wanted to alarm someone who maybe want to upgrade that there is issue with installing on a non-cloud-mini debian 13 os and it does break panel out-of-box, while ispconfig claim compatible and recommended to use with 13. If you call it hijacking, then im guilty of it.
    I would just report it on gitlab but after some time my account wasn't even approve, its fine, more people hit forum than issue tab on ispconfig gitlab.

    the main issue that breaks panel comes from bad perminisions that are not explicitly set, first there is locking line on a file that is not created, later there if wf function that created file with content injection, setting +x rights, and then seting locking attribute once again. The fix would be ajusting just one line - which would not break cloud-flavor images and fixed base image thing.
    Issues with resolve end installer with abort which is very correct behavior. the rights issue does not stop installed but breaks access to panel.

    its not resolveconf issue that breaks panel, thank you
     
    /dev/null/, Jan 31, 2026
    #6
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    Misinformation is when a user, like in your case, tries to mislead other users do wrong actions on their servers. You have an installation issue, which I said I would look into in the other thread. Your installation issue is completely unrelated to upgrades. So you're posting it in all Debian 13 update threads is thread hijacking.

    Then you repeat over and over the false claim that I tested on cloud images only, which I never said. You should have better asked if I tested on cloud images instead of posting such false claims. I actually tested my own root servers, my own cloud infrastructure, which is KVM-based with my own images, and on some cloud systems as well, but not using any cloud distributions. Btw, we already have a few thousand successful ISPConfig Debian 13 installations. It's funny how you think the whole world must turn around you just because the installation failed on a base installation image you have built.

    But as I said, I will look into the issue and see if I can fix it.
     
    till, Jan 31, 2026
    #7
    /dev/null/ likes this.
Thread Status:
Not open for further replies.

Share This Page