Posts by Catscrash

So, I double-checked it. The weird thing is, that the reseller and the customer even do have an unlimited email quota.

As soon as I changed the value on the normal-email tab to any value > 1, it works for forwarding mail as well

actually I noticed that too, If the quota on the "normal email" tab is set to 0, and zero is not allowed (at least I suppose that in this case my customer was not allowed to set an unlimited quota) it complains for forwarding mails as well, although this setting should not matter for forwarding mails

working perfectly with the new version, amazin! thanks a lot

Do you already know, when a version with the new possibilities will be online? I'd be happy to "beta-test"

Have a nice vacation.

Somehow I didn't get a message that you answered, sorry!

First, the new interface looks perfect, thank you!

Second, thanks for your BTW-info, that's actually working great

that is a LOT of domains Looking good

Quote from Nuxwin

It is clear enought for you?

that's perfect!

absolutely, that looks great

Quote from Nuxwin

So, here the only thing we can do is adding a textarea for subject alternative names but it will be available at admin level only, and only for the panel and services SSL certificates.

that would be exactly the thing I would like, but I see and understand your concern. The limitations wouldn't be an issue for me, since it's quite small and I wouldn't hit either limit, but I get, that you have to look out for the big customers as well.

Thanks for your post, and if you do plan to create such a text field in the future, I would be very happy

Hi!

I would like the customer to be able to call the panel using his own domain. Let's say I use

panel.hosting8.example:4443

but the customer has custdomain1.de and I want him to be able to use custdomain1.de:4443. nginx doesn't bind to a specific domain, so that's not an issue, but of course the not-matching certificate is not nice.

This would be especially nice, since the webmailer runs here as well, so the customer could do a webmail.custdomain1.de -> custdomain1.de:4443/webmail redirect himself and have the "trusted" domain in the URL and not something unknown.

Let's encrypt supports this, I used this like I said before manually (and you already use it for the www. alt names, so I guess part of it would already be ready in the code?), I think it would be enough, if there was like a text box where you could enter alt names for the certificate before the activation - I also think it would be enough if that would be possible for the panel, it would not be needed for the customer domain certificates.