Which command did you run? You wrote “trying to generate a certificate using default process” — but what’s that?
Is it e.g.
./letsencrypt-auto certonly --test-cert --standalone
or is it
./letsencrypt-auto --apache ...
or … not nginx?
I’m wondering if when the lets-encrypt server attempted to contact your server at www.webtechnologycodes.com, then your server wasn’t up and running, for some reason. Perhaps you had a firewall that blocked incoming traffic? Or perhaps there’s some other earlier letsencrypt error message that tells you that letsencrypt failed to (re)start the letsencrypt stuff on your own server? So there was nothing listening on port 443? port 80?
Apparently your server is up-and-running right now anyway on port 80.
(I’m a letsencrypt newbie; all this might be wrong)