Now, both the two servers are answering correctly. Update took place.
Yes, but I can’t click continue in Plesk because it logs out and I have to log back in and start back over again…so letencrypt is looking at ns1 and its not there…so it fails and by the time it is there, Plesk timesout.
You should keep Plesk busy with some unrelated, fake input to avoid time-out.
Good idea, I will try that.
Exactly what it was. I waited until ns1.netfirms.com was showing correct txt as ns2 and I played with Plesk so it would not timeout… took 15 minutes, hit continue and voila.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.