Search results

Used this a long time ago when something similar happened.. yum-complete-transaction package-cleanup --problems package-cleanup --dupes package-cleanup --cleandupes rpm -Va --nofiles --nodigest yum clean all rpm --rebuilddb yum update

Update: Just received the bounced email header. Looks like the forwarded domain email was being sent to port 25 on the Plesk server which is closed so the email never arrived. Not sure if the last 2 Plesk updates closed port 25, or the VPS host closed it or the registrar changed port to 25...

Scenario: Domain1.com hosted on VPS server secured with Plesk and inbound/outbound POP email works perfectly Domain2.com is a domain only used for receiving email with no hosting so domain registrar forwards all email from Domain2.com to Domain1.com This has worked perfectly until Plesk...

How to change Powered by Plesk logo in the header and the footer text?

I also made this error myself on a new server install and had this issue. Easiest thing to do was reinstall CentOS 7.4 and upgrade MariaDB to 10.1 using the instructions on the MariaDB website. No issues and fast on Plesk 17.5 Attempting to downgrade could throw errors in the future due to...

Contribution - TUTORIAL: downgrade MariaDB 10.2 to MariaDB 10.1

According to the Plesk compatibility page, Plesk Onyx is currently only compatible with MariaDB 5.5, 10.0 and 10.1 Software Requirements for Plesk

This is typical for Hotmail and has been like this for years. You need to whitelist your IPs with Hotmail's SNDS system which will cover you for Hotmail and Live.com Microsoft mail. Takes some time and you'll digitally sign some forms, but your email will flow to Hotmail inboxes. Begin with...

Easy fix -- Log into your server's hosting panel (not Plesk) and change your reverse from 238628.vps-10.com to mail.soup2nuts.biz and your reverse will match your email. Checking the reverse of your hostname shows the 238628.vps-10.com which will change once you're changed your reverse DNS.

Check that your IP is whitelisted in Fail2ban (if you're using it) and check this site Loading site please wait... to fix your 502 error.

Those that have updated, have you checked your live domains using NGINX are still serving SSLs with ALPN and NPN including HTTP2? Bug 1478662 – rebuild for ALPN support Second concern is that i686 files are being downloaded with x64 files (see #3 in the known issues list) as they're telling us...

Can you also post your OS and PHP version?

DKIM headers are removed when email is forwarded through GMail. In fact, when you get your DMARC reports tomorrow, you'll see a FAIL for DKIM on any email that is forwarded to another domain (eg. abc.com -> def@gmail.com). This drove me nuts as well, thinking my DKIM settings weren't correct...

Did you whitelist your IPs in Fail2ban including 127.0.0.1?

Apache keeps going down: server reached MaxRequestWorkers setting

You've only got 2 ports open on your server (22 and 995). Not sure if you're running CentOS or not, but here's what we do on OVH every time we purchase a server: - Let OVH install the OS and Plesk (they'll install an ancient Plesk version) - Log into your OVH Panel and reinstall the OS (such...

Will installing the perl-DBD-MySQL file have any affect on the MariaDB database or anything else on the server we should be concerned about? Also running CentOS 7.3.1611 and Plesk 17.5.3 Tried adding the [Service] file to the MariaDB config and reloading daemon and mariadb but still got the...

I see it every day as well, and only on the first login of the day. The date in the updated box doesn't change (unless there's been an update) but the green banner shows every day whether there has been an update or not. Doesn't bother us -- it's just there every morning.

Searching the forum and finding this post https://talk.plesk.com/threads/error-dr-web-updater-failed-to-download-files.341656/ which we have followed, we continue to receive the Dr Web email error each day. We can run the update manually with success via ssh but this has issue began a week ago...

The error began about a week ago and we receive an email every day about the error. Logging into the server and manually running /opt/drweb/update.pl downloads the files and everything is OK. Next morning the error returns. How do we resolve this and stop the error from occurring?