turns out it was actually a DNS issue. might be my router, but not sure the exact cause
tried nslookup for launchermeta.mojang.com {{}}
> launchermeta.mojang.com Server: [10.0.0.1] Address: 10.0.0.1DNS request timed out. {{ timeout was 2 seconds.}} DNS request timed out. {{ timeout was 2 seconds.}} DNS request timed out. {{ timeout was 2 seconds.}} DNS request timed out. {{ timeout was 2 seconds.}} *** Request to [10.0.0.1] timed-out
changed my dns server to google's DNS servers (8.8.8.8)to see if it fixed, it did. (as did a bunch of other dns providers) so either mojang changed the DNS registration and it has not propagated through all servers, or routers DNS is not working entirely properly.
My router is
Firmware Version:
3.15.3 Build 180114 Rel.39265n
Hardware Version:
Archer C7 v2 00000000
TLDR - changing DNS server to not use router fixed issue.
Andrew Moskevitz
experienced the same problem,
turns out it was actually a DNS issue. might be my router, but not sure the exact cause
tried nslookup forlaunchermeta.mojang.com{{}}
> launchermeta.mojang.comServer: [10.0.0.1]Address: 10.0.0.1DNS request timed out.{{ timeout was 2 seconds.}}
DNS request timed out.{{ timeout was 2 seconds.}}
DNS request timed out.{{ timeout was 2 seconds.}}
DNS request timed out.{{ timeout was 2 seconds.}}
*** Request to [10.0.0.1] timed-outchanged my dns server to google's DNS servers (8.8.8.8)to see if it fixed, it did. (as did a bunch of other dns providers)
so either mojang changed the DNS registration and it has not propagated through all servers, or routers DNS is not working entirely properly.
My router is
Firmware Version:
3.15.3 Build 180114 Rel.39265n
Hardware Version:
Archer C7 v2 00000000
TLDR - changing DNS server to not use router fixed issue.