Linuxmuster-setup läuft nicht durch (SSH-Verbindung zur Firewall)

Hi. It’s really strange … but I think that only @arnaud can see if this is a bug or a issue with your special setup.

If you’re starting from scratch with Proxmox, I’m keeping my fingers crossed that things will work better. I don’t think you’ll regret this decision, as many things work perfectly…
Getting started isn’t that complicated. The server is up and running in a quarter of an hour.

Did you check if there are more detailed messages in /var/log/ajenti/ajenti.log? (I can’t check this file here at the moment.) And the message Can't open PID file /run/ajenti.pid is strange too (as it was a problem a very long time ago). That’s why @arnaud can possibly take a look at this problem :man_shrugging: :interrobang:
But as we have all already noticed above, there’s still something wrong with the certificates and the ajenti-crash-log confirms that too :thinking:

Next time I’ll be in front of this test machine only on Monday, but in post #104 (and earlier in #99) there are the contents of the ajelnti.log and crash.txt files.
What I will be able to do over the weekend (maybe tomorrow) is to set up a test system at home on real physical machines to see if the error can be reproduced, whether it is related to physical machines or to a specific wan network…

i looked again in the picure of your cert folder…
I do think the trefortserver.fullchain.pem is not correct either
those certificates, I think are created with the cacerts… and there u have a mix of different dates.
the current dates of cacert.pem is May22nd and the cacert.key is May20, while the trefortserver.fullchain.pem has a date of May20. so i suppose it was created with a different cacert pair, I suppose.
the firewall is working for you… but thosed certs all of may 22nd as a date
so my guess would be to recreate the trefortserver.fullchain.pem and then the bundle

also there is this server.fullchain.pem file with 0 bytes. is that a file that is not used,since u renamed the server or sth.? I dont understand all what happened here, sorry…

Hi. Yes … there’s something mixed up … if you want to use a real FQDN for your server (and not *.lan) you can also try to let OPNSense create all certs for you (see #82).
:man_shrugging:

Yes, I noticed that too (the 0 byte file was created by the renew-cert script), so I did a fresh install on Friday, so all cert files are dated May 23rd, but I didn’t take a fresh screenshot of that one because it didn’t matter (I tried the fresh not yet messed up install as described in #113).

Well, I put together a test system at home with 2 physical machines, the result is similar, the server ssl authentication key pairs are not created during websetup. The situation is even worse here, that after creating them manually, I set up undbounded dns, but the server can’t see the net at all, but it can’t ping or resolve names, and sophomorix device import fails if I want to import the server and firewall. EDIT: I correct myself, I just had to wait a little longer for the import, but then the result was exactly the same as on the school test machine, so I managed to reproduce it exactly.

So we can probably rule out a network specific error, but this still leaves the physical machines under suspicion, maybe someone else could confirm, if you have the time and energy, next week I will come back with a Proxmox test.
The base is a Ryzen 7 5700G 64gb ram, 2x512 nvme ssd, 2x3 tb sata hdd machine, I guess I’ll add a network card (+1 I guess will be enough? ), so I guess that’s enough for the Proxmox+opnsense+lmn trio, of course I don’t know what settings I should install, I’ll have to check that first, and if I manage to install it I can set up another machine as Proxmox backup, where I can save data, snapshots from time to time…

I think it should have been noticed by now if this was a bug that left the system unable to run. I’m not 100% sure … but I think Chris (@cweikl ) recently installed v7.3 from scratch, right? He should have noticed something similar to your problem :man_shrugging: :thinking: :interrobang:
I’m gradually running out of ideas … but:

… we can help you with Proxmox and of course the backup-concept (maybe with a „proxmox backup server“ (PBS)?) What kind ouf NIC do you use in the server? Is it 10 GBit or 1 GBit?

Now I tried to follow the websetup process directly, when it says ssl certs were successfully created, I looked in the ssl folder on the server and of course the server cert.pem was not there and then not even bundle, it is created 1-2 minutes later from these incomplete files.
The internal network is 1 Gbit and the server has 1 integrated Gbit network card, I can add up to 3 more 1gbit pci-e cards but I guess 1 should be enough, maybe 2 I don’t know if the Proxmox needs a dedicated one. And yes I would think about PBS once I get to a working system worth saving. :face_in_clouds:

In this case one of the developers (@Entwickler) must take over the problem.

Proxmox-Server: We use at least 2 NICs here. One for the Management-VLAN (Proxmox UI on Port 8006) and the other one for the connection to the Layer3-Router / Switch. But you can keep it simple for the beginning and put the Proxmox-server together with the v7-server and the virtual OPNSense-firewall in the same subnet. That’s easier for the moment…

Ok I’m going to start the Proxmox installation, first question for 2x512gb ssd and 2x3tb hdd can I choose between zfs raid1 and zfs raidz1, which one is better?

Mirror is better

Ok then, raidz is out, before I get too deep into exactly what it is :sweat_smile:. I have plain raid1 mirrors in zfs and btrfs, does it matter which one I choose?

Does it mean that you already have a RAID (Controller) in the server??

If you just connect your SSD drives to a HBA I would choose zfs Mirror.

No, I’ll just use software raid, then I’ll simply create a zfs raid1 array on the ssd’s and then Proxmox will go on that, the HDD and raid can be created later under the already running Proxmox I guess.

OK, then it’s ok … never combine hardware RAID and ZFS

Thanks, according to the description I got to the network bridge setup quickly, now I have to set up the disks, but it works completely differently than I’m used to, and the description only mentions a single drives, and I would be operating with 2 raid1. What the Proxmox created zfs raid1 is visible on the ssd storages, and on the hdd’s the former linux one is visible on the mdadm software raid unpartitioned , how can I import this into the system, and how do I create virtual drives on the ssd raid array?

I think it’s time to start a new topic with this problem as it has nothing more to do with the other one … maybe you can restart as I don’t have the rights to split a thread.

btw: I’m not used to sofware-raid as it is not necessary on proxmox … I always install proxmox as it is and let the system create the storage later. Look at Datacenter → Storage → Add …

Yes it’s clear that virtual machines/drives don’t need raid, the host Proxmox runs on it, I’m just a complete noob at setting this up, I guess this datacenter is not part of the base packages, it has to be added afterwards from another repo.
Let’s say the end result of the installation could eventually belong in this topic :slightly_smiling_face:, let’s say the title is ssh, but basically it was about ssl in the end, I’ll open a new topic for beginner Proxmox questions. :blush:

No …

OK, I found it, and I was able to create the zfs raid on the sata hdds, but first I had to delete the previous raid from the command line. I suppose I should create the virtual storage here, but I’m still getting familiar with the interface. Tomorrow I think I’ll continue from here and create a separate topic for it then.