CLIENT AREACall Us 1-800-383-5193


Call Us 1-800-383-5193


Call Us 1-800-383-5193

Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Plesk Webmail Server Not Found – How to resolve

by | Apr 23, 2021

Stuck with the error, Plesk Webmail Server Not Found? We can help you.

If the Plesk server is not set up to manage DNS the Webmail will not resolve correctly in the global DNS system.

As part of our Server Management Services, we assist our customers with several Plesk queries.

Today, let us see an effective way to resolve this error.


Plesk Webmail Server Not Found

Generally, we come across this error while opening webmail/domain in a browser or when we issue Let’s Encrypt on the domain.

The error message may differ based on the browser we use. For instance,

  • Firefox:
“Server not found. Firefox can’t find the server at”
  • IE:
“Internet Explorer cannot display the webpage”
  • Chrome:
“Oops! Google Chrome could not find”




“404 not found”
  • Let’s Encrypt cannot be issued on the domain:
Error: Could not issue a Let’s Encrypt SSL/TLS certificate for Authorization for the domain failed.
Type: urn:acme:error:connection
Status: 400
Detail: Fetching Timeout during connect (likely firewall problem)



To verify the root cause, we run the following commands in a command-line interface.

Initially, we test if the domain can resolve to an IP address in general:


Non-authoritative answer:

However, if we receive the following output, it means that the domain does not resolve properly:


*** UnKnown can’t find No response from server

Then, we check if the DNS service on the server with Plesk contains a proper record for the domain:

nslookup <—- IP address of the server with Plesk
Server: UnKnown


Here, if we receive a wrong IP address or nothing at all from the first command, and valid records from the second command, it means the Plesk server dos not serve the DNS zone for a domain.

There are two options to resolve the issue:

1. Set Plesk server to be nameserver of the domain

Generally, we install the DNS Server in Plesk Installer.

If it is not, we follow the steps below and add the DNS Server component to the Plesk configuration.

  • Initially, open UDP port 53 on the system and external firewall.
  • Log into Plesk and find Name Servers in Plesk > Domains > > DNS Settings, take the “value” for the record type “NS”.
  • Then, change the Name Server for our domain at the domain registrar’s account.

Some domain registrars require two NS servers with different IP addresses. In such cases, we may experience a problem.

To solve this, there are different ways:

Firstly, we can allocate an additional IP address from the Hosting Provider and add it to Plesk. Then use it as an additional Name Server in domains DNS Settings.

For example,

On the other hand, we can set up a slave DNS server on additional hosting and connect it to Plesk as a Slave DNS server using the extension.

Similarly, we can use 3rd-party extensions that allow adding DNS zones: Microsoft Azure DNS, DigitalOcean DNS, Amazon Route 53

To find it, go to, Menu Plesk > Domains > > DNS Settings should be available.

Plesk Webmail Server Not Found

2. Add a respective A-record on a registrar/3rd-party DNS side.

[Need help with the resolution? We’d be happy to assist you]



In short, ‘Plesk Webmail Server Not Found’ occurs while opening webmail/domain in a browser or when we issue Let’s Encrypt on the domain.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *