Search results

The version of Plesk is Obsidian (latest version available) - this issue still happens for me regardless of version. Most of our servers are running Obsidian. For one domain (subscription) in Plesk, we need to secure the website, mail and access to Plesk via the domain on port 8443. That's it.

Okay, thanks for your help - this is what I wanted to know, what my options were.

That's not what I am trying to do - I think you miss the point of my post. Plesk can be access over https fine at the hostname - I was just wanting to know if it's possible for subscribers to access Plesk at their own domain names using the Let's Encrypt SSL certificate.

Um... I am !? It's pretty common for a business to access their control panel on their own domain name.

That's the case for us as system administrators but what if clients want to access their control panel on their domain name? Like domain.com:8443 ?

I'll give a typical scenario:- Plesk on a server being used to host multiple customers (subscriptions)... Hostname is like: server-id.myhosting.com I have the Let's Encrypt SSL certificate securing Plesk at server-id.myhosting.com but then Plesk flags as unsecure when accessed via any of the...

30k queued emails!? :oops: Sorry, I don't the answer to your question but it might be useful to provide the version of Plesk you're using and on what OS. I would have thought the sort preference would have been stored in the browser session (cookie) so surprised that trying a different browser...

Ah this makes sense. Thanks for explaining that. So basically, there is nothing I can do about it from my side?

Okay thanks. It's not really a pressing issue as when I log into Plesk, there is no issue with the key/license (it seems to fix itself) but when I get a chance, I will send a message via the form you linked me to. Would be interested to see if anyone else replies to this thread with similar...

I asked it more of a query for discussion rather than needing support - unless this needs support (which I don't think it does)? I just wondered why this keeps cropping up - we've noticed it on numerous different servers over the years. Was just wondering what causes it.

Every month I get an email notification that is like: Unable to update EXT.05688703.0010: an error occurred while processing your key. You can try to retrieve the key manually in Plesk (Tools & Settings > License Management) or let Plesk try to update it in the next 24 hours. If you do not want...

My question is typically aimed at those companies that run multiple instances of Plesk on multiple servers which host many websites. What extension or set up are you using for antivirus/malware scanning on your servers? We've used a combination of all sorts in the past but we'd like to...

Interesting. Strange as normally in another environment, those Nginx rewrites should work (I'm not sure I've set them in Plesk directly before though). Thanks for your reply though. Maybe someone else might know how to get them working but in this case ,I won't stress too much as they'll be in...

We've got Plesk Obsidian set up on a dev server and we're building a Magento 2 websites which requires a couple of temporary URL rewrites set up before the website gets migrated to the client's server (which will be running Apache and the rewrites set up in .htaccess). I don't believe we've...

Thanks for the info @learning_curve - definitely sounds like upgrading to Obsidian is easier :D

I wasn't expecting that to work because I've experienced the same issue on another server running Obsidian (I actually thought this one was when I originally posted in this forum category). But however, I have now got this sorted and for the benefit of others visiting this thread, the one...

I am not sure why the image above is not working but the URL for it is this: https://i.ibb.co/tpY40fs/domain-specific-le-ssl.png

Yes, it is exactly the issue I can't fix. The issue seems to be that the certificate for webmail seems to be getting picked up from the Plesk 'Tools & Settings' page (which is set to 'Lets Encrypt certificate from server pool') instead of the one set in the domain 'Mail Settings' which is set...

I already have that set and if I run the command on the command line, it returns the common name as the VPS hostname as expected. So all that does is verify that the problem is what I said above. The common name (hostname) is different to the client domains which is why the security warning is...

This has been a problem for a while that I've never managed to figure out... Say we have a VPS running Plesk with 20 different client's hosted,we have secured everything for one client domain using the Let's Encrypt SSL certificate and whilst this works fine in any tools and browser directly...