Search results

Instead of creating example.com in Plesk, create test.example.com in the same way. So create a subdomain as if it would be a domain. If you already created example.com, you could simply rename it to test.example.com.

I'm afraid I don't have a direct answer to the question. For those that might wish to do the same and aren't aware: please note that having a CNAME set for the root of the domain is not recommended for several reasons. One of them being that, as per RFC, if a CNAME exists, a CNAME must be the...

Well, depending on whether the majority of your customer data lies in web pages, email contents or databases, you could use a new volume for one of those locations. It is hard to say if this a viable approach without knowing the details. Switching to an altogether bigger server instance might...

How to make Plesk interface accessible over a hostname without entering the port number on a Linux server

On CentOS 7 it is indeed: [user@server /]# ll /var/lib/php total 12 4 drwxr-xr-x 3 root root 4096 Nov 1 17:06 . 4 drwxr-xr-x 37 root root 4096 Apr 6 2019 .. 4 drwx-wx-wt 2 root root 4096 Nov 10 19:46 session I'm not sure about CentOS 6 as we've migrated away a while ago, but...

It seems that customers have doubts about the methodology that was used to come up with some of the recommendations. Perhaps a blog about how this was decided would help? A comparison with free and open source alternatives to paid recommendations, an explanation why the score is calculated as...

Please also post the result of: ls -als /usr/sbin/sendmail.postfix ls -als /usr/lib/sendmail.postfix Anyway, while I don't have a test server handy right now, this should solve your issue (all the lines must be entered one after another before you'll see any response): alternatives --install...

BTW, if you'd like to compare the state of MTA alternatives on your server: [user@server /]# alternatives --display mta mta - status is manual. link currently points to /usr/lib64/plesk-9.0/qmail-sendmail-wrapper /usr/lib64/plesk-9.0/qmail-sendmail-wrapper - priority 90 slave mta-sendmail...

Could you please post the result of the following commands: ls -als /usr/sbin/sendmail ls -als /etc/alternatives/mta alternatives --display mta

Which provider told you that there are no port 25 limitations? The limitation can be on either side, the network you're connecting from and also on the network your server is on. Both is quite common these days... The odd thing is that the connection succeeded for a short while. Did you check...

It seems that these symlinks are problematic after Obsidian upgrades. The above is OK, but since RHEL/CentOS uses "alternatives" for such things, this below might be more correct and perhaps prevent some unforeseen troubles in the future... This is actually from Plesk Onyx, CentOS 7 and qmail...

Do you have the plesk-php73-devel package installed?

I guess these are an unfortunate but somewhat expected consequences when doing backups of a live site. As to whether the backups are fully restorable... I don't think there can be a definite answer to this, as it depends on a particular case. Backups might be fully restorable technically, but...

Well, which OS and OS version are we talking about...? Are you the server admin or a customer? Apart from Plesk being installed, your server is basically a linux distro that could also be used as a workstation, for tasks such as this. That being said, the question to ask yourself at this point...

So Gmail is treating your emails as spam? The 127.0.0.1 you're seeing in connection with webmail is OK, don't worry about it. Also, your SPF, DKIM and rDNS seem to be in order. I have also checked if the IP 207.180.207.212 is included in spam lists and it seems to be clean. That's about as...

There are at least two different php.ini on every Plesk server, one belonging to the operating system's PHP and the other belonging to Plesk's PHP. If you've installed alternative PHP versions that come with Plesk, there is one more for each PHP version installed. In any case, I suggest...

Users get logged out from where, the Plesk interface? Which php.ini did you edit?

I think these warnings might be safe to ignore. Proceed with the build and see if it finishes without errors...

This might be a bug. Can you please also post the list of the registered PHP handlers?

I have some experience running Silverstripe sites, albeit older ones, and they can be troublesome when it comes to the open_basedir and set_include_path. Often the errors Silverstripe throws aren't what they seem. Did you try: {DOCROOT}{/}{:}{TMP}{/}{:}/opt/plesk/php/7.3/share/pear Also...