The order is ready:
https://acme-v02.api.letsencrypt.org/acme/order/44256591/129845298
So the order and challenge validation works. So your ip-configuration isn't the problem.
The finalization step produces the timeout.
Your Certificate request:
Summary
-----BEGIN CERTIFICATE REQUEST-----
MIICcjCCAVoCAQIwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOMA
ASZsVuGJQTADA8/2fKy1cnL8m7dog1z57RSmmLdG0dbcsH0ziitFKHwIUWQctBta
UGNzG8V1bkCBFoRGhtq6N6MrZ1bT5l1AaI+PbDt1dAMcNOXaG658FtVwmcfNAm6s
5sTflb51fiMqZ/CcTShXT6Kh1qbMibhn+68faxUq7xkmLYCa8axYdC15bgwtMo+q
4ZunR2fTgSLKdniY6hrhz2yB9INPJkRq8h597W8YIvKhlQzCSkxWwzdJoGrnoQrs
wKHUIFhbJRmpl9AbQ7ylbVDMQOyZg9Y9roD8cdycn/xs7nWvFdIsiTDLoXykEUmu
jBgvfd5jaxwNytMOcrkCAwEAAaAtMCsGCSqGSIb3DQEJDjEeMBwwGgYDVR0RBBMw
EYIPZ2FtZWNwLngyYzAubmV0MA0GCSqGSIb3DQEBCwUAA4IBAQC90Ql8+1UzqQGC
9QLPgcDAlZLS3ebomWbVq5vUYj7aF1J3S647g7CdkNOnuSnN600Juz89gL5h7tgc
xT347jf32T0ihvDMSv/Rz/GwNtRjgKuFZhbSfeu+Icthv+BhTf7s4gxerGi9TisB
5lzU1pJSrKdZWWbUlS29lHVZwmXTXhjae0jQyFxkR1TrVzNPf6Zzlwc0Tky+ucKr
lDLftXDdTRf9HnJguZ2iwzh3417Nw1NNP1j18Nz3cc+BjEEQu3WAhHJYDZfL9ahH
zyYUoTCf+rG2wfQhZwr/Rnmv7dm03OhX9yaLclkLk8QHgQqm++MYhh8zwhrJGiH2
/FZAZnmD
-----END CERTIFICATE REQUEST-----
looks good, CSR Decoder - Check CSR to verify its contents accepts it.
So it looks like Letsencrypt (1) has a general timeout or (2) doesn't understand your specific Certificate request. But you don't have a blocking or corrupt CAA-entry.
One thing I don't understand:
D:\temp>nslookup gamecp.x2c0.net.
Name: gamecp.x2c0.net
Address: 54.39.202.103
There is a specific A-record, this is ok. But:
D:\temp>nslookup -type=CNAME gamecp.x2c0.net.
x2c0.net
primary name server = chan.ns.cloudflare.com
responsible mail addr = dns.cloudflare.com
serial = 2029182250
refresh = 10000 (2 hours 46 mins 40 secs)
retry = 2400 (40 mins)
expire = 604800 (7 days)
default TTL = 3600 (1 hour)
Looks like you have an A-record and a CNAME-record. Perhaps Letsencrypt want't to check something -> timeout.
Can you remove this CNAME?