Issue Error: Could not get Mozilla tls config: cURL error 6

[DigitalSplendid]

Server operating system version

18.0.49

Plesk version and microupdate number

Web Admin Se Edition

Facing this issue:




I tried running following command on SSH:




Also tried replacing 8.8.8.8 with IP address:



Help appreciated.

 

[GwenDragon]

You need to switch to user root.
sudo su

 

[Peter Debik]

As in the other thread, likely your name resolver does not work correctly. Please check /etc/resolv.conf and change resolvers to reliable ones, e.g. Google's 8.8.8.8 and 8.8.4.4.

 

[DigitalSplendid]

As in the other thread, likely your name resolver does not work correctly. Please check /etc/resolv.conf and change resolvers to reliable ones, e.g. Google's 8.8.8.8 and 8.8.4.4.

Getting the above output.

 

[DigitalSplendid]

 

[DigitalSplendid]

 

[DigitalSplendid]

 

[Peter Debik]

Please try to replace the "nameserver 127.0.0.53" line with

nameserver 8.8.8.8
nameserver 8.8.4.4

then store the file and try pinging or cURLing the addresses again.

 

[DigitalSplendid]

Please try to replace the "nameserver 127.0.0.53" line with

nameserver 8.8.8.8
nameserver 8.8.4.4

then store the file and try pinging or cURLing the addresses again.

Today I could see the SSL activated but the website digitalsplendid.shop showing not connected.

 

[Peter Debik]

Your website is working fine here.

 

[DigitalSplendid]

Your website is working fine here.

Actually, I have transferred a fresh instance.

 

[Peter Debik]

Is this issue solved for you then?

 

[DigitalSplendid]

No, I could not solve. It was getting way too complicated. I believe the system of restoring snapshot from AWS Lightsail is not as perfect as one expects from Plesk. Earlier too, I fell into a similar problem and could not restore.

 

[Peter Debik]

Can you please describe what exactly does not work correctly at this point?

 

[DigitalSplendid]

I was having pollclap.com using Plesk Web Admin edition hosted on an AWS Lightsail instance. Since ownership of pollclap.com domain transferred to a buyer, I used digitalsplendid.shop as temporary domain to transfer the content of the website to the new buyer. Since I erased all the content of pollclap.com due to wrong use of Migrate Guru WordPress plugin, I decided to restore the snapshot. That AWS Lightsail instance had a snapshot taken. As AWS Lightsail restore requires the creation of a new AWS Lightsail instance, I did that. The problem started as the restored instance never worked.

https://www.canva.com/design/DAFlrl3XElo/NpSfIGjeYcvNSxHlih2pHw/edit?utm_content=DAFlrl3XElo&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton

 

[Peter Debik]

O.k., I understand that the new AWS Lightsail instance never worked. What I do not yet understand what that means. What does not work? Derived from your screenshots Plesk is accessible, the website data is present. The only thing so far that I could identify that does not work correctly is name resolution. Is that what your question is about?

 

[DigitalSplendid]

Thanks for the support.
Yes, Plesk is accessible. In no way, I could make the site live. I have tried connecting with domain name digitalsplendid.shop.

 

[DigitalSplendid]

@Peter Debik Could you kindly suggest the way I can connect domain with the website.

 

[DigitalSplendid]

I tried to once again connect domain with the website. This time it is showing 'file not found.'

 

[Peter Debik]

First please check which nameserver is set in the domain. Then check what IP address that nameserver delivers when asked, e.g.
nslookup <domain> <nameserver name>
Is this the correct target IP?
Then check whether Plesk is configured to react on that IP (Tools & Settings > IP Addresses).
Then check what IP the domain is configured to use.
Is this all lined up? Correct nameserver? Nameserver responding? Responding with the correct IP address? Plesk knowing that IP address? Domain configured on that IP address?