Search results

  1. S

    Node unaccessible after upgrading from 2.3 to 3.1

    Glad my failure helped to improve the wiki at least :)
  2. S

    Node unaccessible after upgrading from 2.3 to 3.1

    Hi Marco, yes, I can remember that it said it all was downloaded successfully. That was the Reason to proceed at all. Looked right for me in this Moment.^^ The Odyssey startet with the upgradeprocess itself as it failed because of the lack of internet connection. Greetings
  3. S

    Node unaccessible after upgrading from 2.3 to 3.1

    Well let me give you guys a short update on this. I actually managed to get my Node working again after having a night of nightmares. Here is what I did wrong: I followed the Tutorial on how to upgrade to version 3.1 and got to this point here. ./pve-upgrade-2.3-to-3.0 --download-only I...
  4. S

    Node unaccessible after upgrading from 2.3 to 3.1

    Thanks for that hint, good to know Apache should be useless here by now. I remembered to connect to https instead http and didn't forget about the port either, but thanks for the kind Reminder :) Any more help and ideas are appretiated. grz
  5. S

    Node unaccessible after upgrading from 2.3 to 3.1

    Hey Guys, for two month now we had a cluster of two running in our noise chamber. Both were running Proxmox 2.3 and worked as good as possible as it was configured. The problem started today. We noticed that Version 2.3 is already outdated and were about to realize HA Clustering. We installed a...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!