Search results

Don't count me in the "we": I can't be sure it will have any real effect, but I think the best option we have (maybe beside our paying dollars/euro/rubles...) to redress what we see as important issues/lacks is to have our "uservoice" heard. Never said anything to the contrary! :)

I don't think there is much to improve: just get used to typing "https://myplesk.example.com:8443" or create a shortcut to it... ;)

... and certainly I don't see any inconsistency in pointing out to the user voice request for a correct, integrated, mechanism for requesting Let's Encrypt wildcard certificates from the Plesk panel in a thread where the currently available workarounds (hacks, from the point of view of an...

Of course I did, and I don't see any inconsistency in having: Plesk already working (maybe...) on it A "popular" request for this being implemented If you consider that it is very unlikely that Plesk can count on unlimited coding resources, a widely supported "uservoice" request can help them...

There is a feature request for this: Wildcard for Let´s Encrypt Please vote for it!

... and actually I forgot this is a feature request I already voted for! (Alzheimer, I guess...) Please vote for this: show let's encrypt certificate expiration date

Not only that: if you make an habit of accessing the administrative interface through the redirection set up in the .htaccess of the "normal" domain, you will not be able to access it the day that your Apache or Nginx servers are down. That's probably not a big issue if you're the only one...

I see this is flagged as resolved, but no explanation on the "how" is given: is it really solved? If not, I think you're better off contacting Plesk support for this kind of issue...

Flagging that as the "Best answer", as it seems to be more informative...

Thanks @Brujo I just tried installing "Advisor" in Plesk 17.8 on my test VPS, and indeed (under a deep layer of up-selling and other things I adamantly call "spam") that information is available but in a different format from the one you showed: just a "Vaild to:" field". There are anyway zero...

Am I missing the "how"?

I think you're up for a bad surprise the day your Apache or Nginx services will stop functioning (for whatever reason)... I think there is a very good reason for keeping the administrative web UI decoupled from the domain's web servers.

Hello! I'm in the middle of my first round of Let's Encrypt certificates renewal (automatic) and apparently everything is going OK, but I just noticed the lack of some important information (or maybe I haven't noticed where to look!): Is there a way in Plesk Panel to display certificates...

In case there are others following the thread and the @G J Piper issue: I had an email exchange with him and had access to his interaction with Sendgrid. What emerges is that Sendgrid (for reasons I can also agree with...) is not willing to alter in any way the content that is "handed to them"...

... I'm starting to think that all this SPF/SRS s*it is essentially flawed, as it is demonstrated by your case (issues with remailers/forwarders): a valid DKIM signature of the original message should be all that is needed... or am I missing something?

... just an idea, to (possibly...) nail them to the wall: for one of the domain you're hosting (maybe a sub-domain so that you do not create problems to an active domain...) set up a DMARC policy with p=reject and then try directly (e.g via Roundcube) sending mail from that (sub-)domain to GMail...

@G J Piper I'm sending you a PM with my email address so that you can forward me the Sendgrid answer in order to more easily access the documents they're citing: doing that from the jpeg image is a huge pain in the back... Anyway, from a first look, I'm seeing some fallacies in their answer...

... and I'm ready to bet that of the 48 viewer of this thread at least 45 are still asking themselves what "OSS" means! Heck, I even looked up in Wikipedia: OSS - Wikipedia (but I understand "Ovary Sparing Spay" can be ruled out...)

... but Alibaba is Chinese stuff, not Italian: in Italy we are already enough afflicted by "Aruba"

... but TBH, at least in my usage scenario (CentOS 7.4, Web Pro Edition, Apache, Nginx, Postfix, Dovecot, Roundcube), I'm finding it quite stable (although not "officially stable") after a couple of initial hiccups and definitely a step forward from 17.5.3