Recent content by Shamrock

Next step probably. So does www.internet.nl btw. Hence we need to rely on such lists to get the best possible outcome. I'm not a cryptologist and don't have time to read all those publications. Risk based, this was the best/reasonable outcome without limiting access too much for (potential)...

Thanks, Plesk support actually noted the same thing this afternoon. Looks like they may have it under development as well. Would be a good thing to have this, likely based on the cyphersuites.info list. They were also kind enough to translate, where necessary, the relevant algorithms from IANA...

At least not with the first answer, 301 response. Same goes for HTTPS redirect. Same goes for HTTPS redirect. So if your premise would be correct that the primary config is applied to the alias domains, at least in these 2 cases, that's not what tests show. In short, and I know it won't do...

Thanks,tryingto find something like this, I presume it will remove cypher suites as well? , Obviously noted regarding bad clients (FYI I have been in the security field for 25 years ;) ). That holds for all connections, even worse for e-mail security protocols like SPF, DKIM, DMARC. If the...

Hi, Is there a way to set HSTS and HTTP/HTTPS redirect options for an alias domain? The main domain has the options set, however the alias domains seem to ignore or don't work in a similar manner it seems. It is impossible to set them on the alias domains as the SSL certificate, and associated...

Yeah I know, I thought there may be an easier way considering the option was A) there before apparently and B) it would be much easier to use the Mozilla config generator to set this up instead of having to type out the entire config line as the docs suggests (which obviously comes with the risk...

Looks like that option is no longer available within the Plesk panel. Any alternative suggestion to get the Mozilla template imported as default cypher suite within Plesk? Anybody tried the Mozilla SSL configuration generator for this...

For those coming across this, the official advice (and I have to concur for now): Whatever you do: DON"T USE wp-toolkit for multisite cloning, that is until Plesk fixes their multiple bugs. That's almost 2 days of work lost and requiring another $399 (regular price) plugin to solve what I hoped...

Update: There are multiple bugs in wp-toolkit when trying to clone a multisite to another subdomain within the same subscription. The error is just the symptom of a lot of stuff breaking behind the scenes, including hostnames being rewritten incorrectly and others not being rewritten at all. If...

Looks like there is a bug in wp-toolkit that is causing this behaviour. Plesk support is going to try a fix tomorrow morning. I will update this thread with the details as soon as that's complete and confirmed to be working.

Update: clearing the WPT cache doesn't resolve the issue, unfortunately.

Before moving our staging, newly build, website to production. I wanted to move the current production website to the dev.example.com subdomain. The move seems to be done well, all documents seem to be present. Even the maintenance state was copied over. However: * wp-toolkit keeps reporting the...

Confirmed. Apt-get no longer provides the offending issue. There is stil an emunify*.list in the apt sources directory its complaining about, but that's only a warning.

Same issue here as well, been up and down for the last months or so. Would be interested in the fix as well, specially for a paid extension.