• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue ssl certificate on plesk resolve on subdomain site... weird thing

nikketrikke

Basic Pleskian
Server operating system version
ubuntu
Plesk version and microupdate number
Version 18.0.55 Update #2
hello i discovered this
i settled serve.domain.com for the plesk server address and issue a let's encrypt certificate...
but if you surf to server.domain.com:8443 appear the plesk login correctly
but if you surf directly to https://server.domain.com
becomes that warning
Screenshot
if you decide to go it redirects to
the subdomain i use for staging site...
that it is very strange
 
Have you created server.domain.com as a domain or subscription on the server? In that case the SSL certificate issued for that domain for the host is different from the one you can (and need) to issue for the domain. Solution: Use the SSL link of the domain in the subscription to create a certificate for that domain.
 
Have you created server.domain.com as a domain or subscription on the server? In that case the SSL certificate issued for that domain for the host is different from the one you can (and need) to issue for the domain. Solution: Use the SSL link of the domain in the subscription to create a certificate for that domain.
hi not... i not create it... i put only on the SSL plesk page to secure server...
I have to create SERVER as subdomain of my main domain and reissue a certificate for that ? as i already did for subdomain Staging?
I CREATE IT and SECURED
Screenshot
now i have to check if all work right
thanks
 
Have you created server.domain.com as a domain or subscription on the server? In that case the SSL certificate issued for that domain for the host is different from the one you can (and need) to issue for the domain. Solution: Use the SSL link of the domain in the subscription to create a certificate for that domain.
sorry not understood well... i have no subscription i have obsidian admin SE 3 domain..
i'm using bunny cdn and need the origin of server to be secured...
i put the ip address of server but it is not secured
so i secure the server with server.domain.com that is the main domain of my site
but i have also 2 other domains in the server...
so now frankly i not know where the bunny cdn can take the origin of the files of the main site..
 
https://prnt.sc/pGU822iqkQF
i have firstly isuued a certificate here without creating server.. domain or subscriptio nor what..
then after your advice i create a new subdomain with server prefix but i think is not the right way
i need the root of the server for the origin for bunny cdn to take the files
 
Back
Top