Search results

Since one of the latest updates I'm receiving backup errors on a daily basis. None of the error message claims holds true - backups are created successfully on FTP space. Here's an example error message: Server Plesk entry point: https://...:8443/ The following error occurred during the...

If you'd read the original post you'd realized that this actually IS about a responsive website, just not in the basic approach of using media queries to shove around existing HTML - instead using a proven technique to deliver an actual dedicated mobile website, optimized only for mobile from...

Ok, once again in this amazing forum so-called experts wave around with their straw man arguments because they are technically unable to answer the question, instead they fall back to sarkasm, trying to make the OP look stupid and other "streetsmart schoolyard techniques" like 12-year-olds. OMG...

I have never asked for a redirect. You're the one that continuously says "redirect". I want to deliver a website at 2 different domains. That is not a redirect.

For the only reason being that you don't answer to my actual question.

Because I don't want to redirect. I want the client browser to remain at m.domain.tld

For some reason CNAME + no subdomain in Plesk gives me the Plesk server default page. Making a Plesk-Subdomain would require to have a file copy of the website in the subdomain directory, wouldn't it? How can I explain it? I want m.domain.tld deliver the exact same website as domain.tld <- the...

It just dawned on me that NOT creating a subdomain in Plesk might be the answer on one hand - on the other I won't be able to handle SSL then.

This is more a "how it's supposed to be made" type of question - rather than "how is it done technically". I want a subdomain for mobile devices: m.domain.tld is supposed to deliver the exact same website as domain.tld. I do not want to make a copy of that website. (The programming of the...

Well "afraid" really is the right term here. I'm afraid it's gonna mess up ~100 business customer email accounts and I'll be blamed and will have to fix it. Another thing I'm afraid of even more, is that it works initially but when I try to remove it 2 years later, it's gonna mess up...

So what would you suggest regarding this scenario: - Install the Kolab Extension on an active production server with customer accounts already present <- do or don't?

Here's why I'm asking: Plesk teams with Kolab for open source groupware So what the article states isn't true?

Please read my question again - I just want to know what's the currents status with Plesk and Kolab. Do I still need to buy it or is it included in a Plesk licence? Is it fully supported or will I have to expect issues if I install or remove it?

Hi! I've been looking to integrate Calender Services and came across Kolab. Seems it's a premium extension, so far so good. But now I'm confused, I came across news articles stating that Plesk is now working actively with Kolab to "provide it for every Plesk user"? On the other hand I came...

Hi virtubox, I'm aware that it's the normal process, I just wanted to know if I'm able to change that behaviour. Does Plesk rely on the presence of the Full Backup to create the incremental one? Two scenarios I'm imagining: a.) I have a "force incremental" switch so Plesk only creates...

My backup space is currently limited so I'm having backups moved from their original FTP-Repo to another location. But everytime I move a "full" backup Plesk will notice and create a new "full" backup - Plesk doesn't know that the full backup still exists only in another location. Can I force...

Bump

So I have a Plesk install with a Login at: example.v123.mywebhoster.com:8443 Problem is, I cannot get a cert for that Domain. I want the Login to Plesk here example.com:8443 example.com is registered in Plesk. I never had to change that myself before, cause it was always configured that way...

The certificate in question was indeed about to expire, so the message by Let's Encrypt was correct. Via the "subdomain workaround" I was able now to renew the certificate. If anyone else is facing the same issue, this is an easy solution: Just create a subdomain mail.domain.tld, select the...

Thanks for your response, but that "dead" cert sn't my real problem - it's just the only error message found in the log about certs. The real problem is the mail.myserver.tld - certificate for which I'm receiving these expiration mails. I'm unsure how to interpret your response, please clarify...