Search results

Thnx, I think you are right. Installing postfix beforehand resolved the issue. Although one could simply remove the citadel stuff after going through the official install guide I prefer a more perfect clean install :-)

I just realized that citadel gets installed on the host. I am not sure for what reason, as least it seems there are unneeded services running like pop3, imap etc... Could somebody explain to me for what citadel is being used inside of Proxmox?

Hm, at least one could interpret your (quite brief) statement that way. If I got it wrong please accept my apology. Anyhow, are you now saying that the created self-signed SSL cert as well as the java applet configuration/sign should include an FQDN? If that is the case, why am I missing this...

I understand the hostname should not be full-qualified in normal cases, that is not my point. I only had the idea if this could be somehow related to my issue with changing the self-signed SSL certificates to those I officially bought from the StartSSL trust center. According to your statement...

Normally it shouldn't. With reference to my post here #1: How can I make sure the correct hostname will be used during installation? I just did a clean install but the resulting cluster node name is still not full-qualified resulting in the java applet error mentioned in my post after changing...

Does that mean the Proxmox install script uses the output of "hostname" or "hostname -f" during installation on a Debian squeeze server? I am currently having issues installing a valid ssl certificate I just bought and have a feeling that it has to do with the former self-signed certificate...

Hi folks, I have a similar issue but I didn't get what exactly needs to be done to resolve it. Here is what I did: 1. Create private key and cert request for *.domain.tld (wildcard certificate) 2. Request new certificate for *.domain.tld from StartSSL 3. Copied cert key to...