Search results

@Sebahat.hadzhi This is not a definition of expected or desirable behavior. If a destination / target server has a different password storage method (hash or sym), then the target server should honor the settings of the source server! Migration of a source also means migration of the...

@mizar This is not desirable. I am not even sure which kind of hash is being used for password hashing - MD5, SHA1, SHA256, SHA512?!?? There should ALWAYS be a method of getting passwords in plain text. It certainly is not the first time that forms to set / reset passwords are used to...

@UHolthausen This seems not to be Plesk specific, but more Debian related, given the failed packages. Are the /etc/apt/sources.list files correct? Kind regards....

@Gjimi, Again, keep it polite. You have an issue that you cannot resolve and, as a result, you are starting a thread that nobody else will post on. It certainly will not help if you become impolite. You do not have to do anything with my posts. A small tip : your Apache alias workaround...

@Denismaster The statement leaves me with the question : external DNS on Plesk servers? Stated differently, do you use an external nameserver provider or do you use Plesk based DNS with "duplicates" on other Plesk servers? The solution that you search for can be obtained by using an...

@Gjimi, That is no surprise. The creation of the LE certificate for the mail server will cause issues due to the existence of the mail.domain.tld subdomain on your server. The creation of the LE certificate for the mail.domain.tld subdomain can and often will cause issues for the creation of...

@Dork Yes, it is possible. Just go to Tools & Settings > SSL/TLS certificates > button "+ Let's Encrypt" (click) Afterwards, assign the LE certificate to Plesk and mail. Before doing all of the above, make sure that 1 - the Custom URL is active, 2 - the DNS zone has been properly...

@Sebahat.hadzhi Not receiving anything. I will try the "if it is broken, give it a good kicking" method to resolve this issue. Otherwise and in the absence of notifications, I will have to assume that my "systems" are clean?!?? Plesk might not be in control of what CloudLinux (or Imunify...

@Bitpalast I did not really follow this topic thread, but saw an issue related to Microsoft mails. Might it be the case that the DANE roll-out on Exchange / Outlook based mail systems cause havoc?!? This (very gradual) roll-out of DANE by Microsoft is really annoying and causing problems...

@kentsmike It might seem logical and/or more secure to access Plesk Panel with [server IP]:8443, but there are some considerations here. If you want to change access for reasons of personal convenience, then I could understand your question. However, in an environment with lots of servers...

@Gjimi, In short, not a SslIt! or Letsencrypt related issue. However, you have created a workaround with respect to certificates .......... and that workaround will create additional issues. In a normal scenario, the following applies : 1 - the mail server is assigned the...

@Sebahat.hadzhi The statement or request is a "thingy" that should be addressed sooner or later. I do not know to which type of custom templates @LRLD is actually referring, but Plesk is (on the one hand) allowing custom templates (for instance, for Nginx) and (on the other hand) failing...

@Gjimi If and when you have a problem, then it is not automatically safe to assume that your problem is caused by Plesk or one of its components. The alleged issue cannot be reproduced in a "normal environment" - with or without external DNS. In most cases, the alleged issue is then not...

@WebHostingAce I do not have that experience that zen.spamhaus.org leads to (too) many false positives. Sure, the occasional false positive may occur, but they are not plenty. The advantage of zen.spamhaus.org is that the list is updated fast. The disadvantage of zen.spamhaus.org is that...

@Kaspar, There has not been a necessity for ages to create separate (mail) subdomains and/or certificates. Nevertheless, SslIt! is still a bit buggy, in the sense that (a) the most recent updates of the extension are bug fixes to a high degree (read: previous bugs were not fixed properly)...

@AYamshanov It is very likely that no STR will exist for the - alleged - issue reported by @Gjimi. The feedback / posts from @Gjimi give an indication that there is no relation with an issue or bug in SslIt! extension (or on the LE side). I have tried to find STR and was not able to...

@Hangover2 I am not specifically responding to your (last) post, but that post contains some valuable comments and also some notes that should be nuanced. First of all, your statement is spot on : it happens a lot (and it should not happen) ....... with all kinds of negative consequences...

This should be addressed properly, it is to some extent a bug.

@Ladylinux , @Maarten, @Sebahat.hadzhi Situation has been changed, slightly for the better, but certainly not for the best. In general, it is not recommend (and not good practice) to create a (separate) mail.domain.tld - keep that subdomain for the mail server, not for domain hosting! In...

@Gjimi It is an incorrect conclusion. I have tested your alleged "bug" and your error notification cannot be reproduced. This is expected, since the LE certificate created will be assigned to / used for the mail.domain.tld too. The error notification that you receive is related to a -...