Issue ipfs daemon on windows 10 , failed to find latest fs-repo-migrations

Help
1

Hey! I try to start ipfs ipfs daemon and then show log , emmmmm

Initializing daemon...
go-ipfs version: 0.7.0
Repo version: 10
System version: amd64/windows
Golang version: go1.14.4
Found outdated fs-repo, migrations need to be run.
Run migrations now? [y/N] y
  => Looking for suitable fs-repo-migrations binary.
  => None found, downloading.
  => Failed to download fs-repo-migrations.
The migrations of fs-repo failed:
  failed to find latest fs-repo-migrations: http.DefaultClient.Do error: Get "https://ipfs.io/ipfs/Qmdo5m6bpQXCayzfGghyvgXJdVHSsXsCKDUo9vWktDKq3K/fs-repo-migrations/versions": dial tcp 75.126.124.162:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
If you think this is a bug, please file an issue and include this whole log output.
  https://github.com/ipfs/fs-repo-migrations

Error: failed to find latest fs-repo-migrations: http.DefaultClient.Do error: Get "https://ipfs.io/ipfs/Qmdo5m6bpQXCayzfGghyvgXJdVHSsXsCKDUo9vWktDKq3K/fs-repo-migrations/versions": dial tcp 75.126.124.162:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

how can I solve this issue ?

2

This seems like a connectivity issue to ipfs.io.

AFAIK 75.126.124.162:443 is not one of the ipfs.io IPs. Can you verify your DNS configuration? The ipfs.io does not seem to be resolving correctly.

3

Does mean that I should configure IPFS DNS on Windows 10 :thinking: