Search results

with "that FQDN" I do NOT mean the FQDN with which you send mail (typically 1 embedded dot)

The first thing you need to do when you start using a server to send mail is to ask your IP-provider for a PTR-record which points to a valid FQDN of yours. That valid FQDN should only have 2 embedded dots, mail.klgiger.com for example Then you have to create an A-record for that FQDN which...

Like most I'm running many sites using virtual hosting on our server. Some of those sites get malicious php-scripts pushed onto them. Luckily these scripts can be recognized easily as they have 'www-data' or 'apache' as its owner. Of course I prefer to make it impossible for hackers to put...

Yes... A pity why they just don't solve it. The "workaround" given actually means we're not taken serious.

It's Plesk 12.0 on CentOS release 6.7 (Final) I think you're right and some CentOS upgrade did that. When I first installed that system I added these folder in /etc/crontab 's $PATH

I don't know exactly how Apple's policy is on updates. I know they just released "El Capitan" and before you could easily upgrade from mountain lion to Maverick, but when I just checked "update" on that 10.7.5 system this morning it told me there are no updates found. Does Apple expect their...

I think most people find it more important that they can receive their mail. From the client side's perspective we're a small firm that has changed their service. They are not interested in that kind of security. Their machine, made by Apple, the inventor of all computers (sarcasm) can never be...

Ever since I've upgraded from Plesk 12.x to Plesk 12.5 I'm getting calls from customers that their mail doesn't work. All these users have Apple mail and use SSL to connect with either IMAP or POP. Thus far I changed their Mail-clients to plain and then they start working again. These are the...

The 1st Change hosting type....

In Plesk Panel's start page is a "Wordpress" section and there one can see all the Wordpress sites. If I disable webhosting of a domain (main domain) that has Wordpress installed (that one was not installed by Plesk, but I'm not 100%) and I return to the startpage of Plesk and select Wordpress I...

I used to have several scripts running in /etc/cron.hourly and they stopped. I investigated this and it turned out that commands out of /usr/local/sbin or /usr/local/bin aren't working anymore because the system can't find these commands. I inspected /etc/crontab and these 2 folders are still...

Plesk 12.5 When I select "Wordpress" from the main menu I got the error "Unable to find service node for web service on domain with id 117" In mysql I gave the command: select id,name,htype from domains where id=117; This turned out to be a domain for which I moved hosting to another server...

OK... Will do it manually then....

I never even considered this to be a problem. Has it always been that way? I never bumped into this in all these years. So now I can't move away domains from that server because all my other servers are 12.0.18?? Edit: and I'm not going to migrate these to 12.5.x yet. The upgrade process...

I don't know how you define source and destination... I invoke the migration on the Plesk 12.0.18 The source of the domain I want to migrate is the Plesk 12.5.30 and the 12.0.18 is the destination.

Destination root@ns6:~# cat /usr/local/psa/version 12.0.18 Ubuntu 12.04 1200150817.13 root@ns6:~# Source [root@ns3 ~]# cat /usr/local/psa/version 12.5.30 CentOS 5 1205150826.19 [root@ns3 ~]#

Yes, I will. On the other hand it would be helpful to me if you tested the feature in your environment and check if it's working at all.

As it was promised that it would get a fix I've let this go for a while. But now it turns out it is still behaving erratically. The way this is being handled is quite poor. It is obviously not working as it should, but during reporting it seems as if I'm hitting a brick wall. The issue at first...

I'm now running 12.5.3 and it still is not working properly... Please advice....

The new Plesk 12.5 came as a bit of a surprise for me and the reason I migrated 1 of my servers to it was a long outstanding bug it is suffering regarding the DNS-server. My server is now upgraded, but that bug is still present. At random some domains get the secondary DNS-server placed in the...