• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved How to check if my DNS record for ssl can be resolved externally

brownbag

Basic Pleskian
When I issue a new certificate using Lets encrypt, I get a message indicating that I should add a DNS record then "before clicking 'Reload', make sure that the DNS record was added and can be resolved externally'. The link takes me to a page that doesn't tell me how to check that the DNS record can be resolved externally. So how do I verify the DNS record. I'm guessing that I somehow use the nslookup command but what would the parameters be?
TIA.
 
you can use nslookup or dig;

nslookup -type=txt _acme-challenge.domain.tld
dig -t txt _acme-challenge.domain.tld
 
you can use nslookup or dig;

nslookup -type=txt _acme-challenge.domain.tld
dig -t txt _acme-challenge.domain.tld
However this needs to be done from another machine 'cause otherwise you'll only see how it resolves internally.
 
Back
Top