Search results

Well, it's a complex question... but in short, yes, it is not trivial. Not impossible, if you're a beginner, but it would be a steep learning curve to get to a some sort of a professional level. It takes time and commitment. If you have the latter and could spare the first, go for it. I suggest...

Just to put things into perspective, how many concurrent visitors and how many daily visitors does your site have? How are your PHP FPM limits set? Nginx? MySQL?

The error looks to be similar but it is not clear if your environment the same as described by @nrep. Have you also changed the hosting plan, causing the certificates to disappear, as originally described? Are your OS and Plesk versions the same as his?

Which command did you run, was the output completely empty? Also, have you specified log-requests = on under the [ext-letsencrypt] section in /usr/local/psa/admin/conf/panel.ini? Do you have any other customized Let's Encrypt settings, e.g. we're using renew-before-expiration = N, where N is a...

If you recall, @IgorG was reluctant to give out a more exact timeline at first. And turns out he was right not to. I'm really disappointed to see a certain kind of replies above. Do some of you think that Plesk doesn't want to release CentOS 8 support as soon as possible? Or what are you...

Spamassassin supports using DNS bloclists as an information source, see here. So just make sure your Spamassassin is configured accordingly and disable the separate spam protection based on DNS blackhole list functionality in Plesk. The latter is indeed intended to work in a way that blocks...

@jmar83, did you try to click "Refresh Now" button on the "System Updates" page? Also, can you still see these updates as pending in shell? I'm thinking that the update might have been executed in the time between the e-mail notice was sent and the time that you've logged into the Plesk GUI...

Perhaps Plesk could just publish the recipe they use for PHP deployments and you can more easily roll your own as needed? This might be something to consider, @IgorG.

Plesk Obsidian supports MariaDB versions 5.5 to 10.3.14. Plesk Onyx on the other hand supports MariaDB versions 5.5 to 10.2.

Well, by creating an alias in Nginx or Apache to a directory, even if this directory is outside of httpdocs, the contents of the directory would become publicly accessible. I assume this is not what you want. If you would like your application to access directories and files that are not...

It's good to hear that you've sorted this out. If there is anything sensitive in the information, I suggest beginning by sending a private message to @IgorG or contacting Plesk Support directly. If not, publishing your finds and getting a possible bug fixed would certainly be beneficial to all...

That's odd. There seem to be a discrepancy between the package database and the OS. Has perhaps samba been installed manually, not through apt? All this and the fact that you've had issues running it, even to the point of rending your server unresponsive, leads me to the conclusion that...

Do you have a "Plesk file server" installed among Plesk Extensions? If you do, do you need it and use it? If not, you might opt to simply remove the Plesk file server Extension, then uninstall the OS samba server package. The troublesome cron script should be removed with it.

Well, if a variable isn't there and it is a valid variable for this version of MariaDB, one can only assume that a default value is used. If you wish to change this, add a variable with a desired value, under a correct section. Just to mention, depending on what you wish to change, it might be...

Since you're using Ubuntu, SELinux is not a likely cause, the common equivalent would be AppArmor. That might be the cause. Especially because a quick look tells me that your directory structure, users and access rights appear normal. The delivery line is indeed missing from the .qmail file...

I assume you mean: 1) if I type https:// domain... 2) if I type http:// domain... I'm afraid it's normal that the https address is not redirected, while http is. Plesk sets it up like this is by design. Consequently, there is also no way to set up a valid certificate for this https address...

@Servus, it was discussed here and a change is considered (tracked as PPM-3074).

They should upgrade to Obsidian. :D

Well, the difference will be in the usage. If you enter e.g. www.website2.com in the form above and issue this certificate to be used for Plesk, then when someone visits https://www.website2.com:8443, there will be no error. But if someone visits https://www.website1.com:8443 instead, he/she...

First, an observation: when you say you're using "sendmail", you are actually using a replacement for the venerable Sendmail program, provided by either Postfix or Qmail, depending on the MTA you've chosen to use within Plesk. Also, the mail envelope and the apparent From: address can differ...