Also, unless you need a wildcard you may be able to use the HTTP Challenge to get a cert. Looks like you are using Apache server which is fairly easy to automate an HTTP Challenge.
With the --apache option you must run Certbot on the server pointed to by the DNS for the domain name requested. Otherwise when the Let's Encrypt server sends the HTTP challenge request to the IP in the DNS that server won't know how to reply. You could do a carefully crafted set of redirects for the acme challenge back to the Certbot machine but if you are clever enough to figure that out you probably would not be here
In this case it had a poor reply with a redirect loop. But, even once that is fixed it won't have the challenge token to properly reply to the LE server.
The faulty redirect loop starts at wineverygame but that sends it to the backup subdomain which then loops by repeating the same redirect
curl -I http://wineverygame.com/.well-known/acme-challenge/Test404
HTTP/1.1 302 Found
Server: Apache
Location: http://backup.wineverygame.com/.well-known/acme-challenge/Test404
curl -I http://backup.wineverygame.com/.well-known/acme-challenge/Test404
HTTP/1.1 302 Found
Server: Apache
Location: http://backup.wineverygame.com/.well-known/acme-challenge/Test404
# the above redirect, if followed continues "forever"
