[gui error report] Error: Initializing daemon...

[sisygoboom]

Initializing daemon... Kubo version: 0.24.0 Repo version: 15 System version: amd64/windows Golang version: go1.21.3 Found outdated fs-repo, migrations need to be run. Looking for suitable migration binaries. Need 4 migrations, downloading. Downloading migration: fs-repo-11-to-12... Downloading migration: fs-repo-12-to-13... Downloading migration: fs-repo-13-to-14... Downloading migration: fs-repo-14-to-15... Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-14-to-15/versions" Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-11-to-12/versions" Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-13-to-14/versions" Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-12-to-13/versions" Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-12-to-13/v1.0.0/fs-repo-12-to-13_v1.0.0_windows-amd64.zip" Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-11-to-12/v1.0.2/fs-repo-11-to-12_v1.0.2_windows-amd64.zip" Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-14-to-15/v1.0.1/fs-repo-14-to-15_v1.0.1_windows-amd64.zip" Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-13-to-14/v1.0.0/fs-repo-13-to-14_v1.0.0_windows-amd64.zip" Downloaded and unpacked migration: C:\Users\chris\AppData\Local\Temp\migrations3772780638\fs-repo-14-to-15.exe (v1.0.1) Downloaded and unpacked migration: C:\Users\chris\AppData\Local\Temp\migrations3772780638\fs-repo-13-to-14.exe (v1.0.0) Downloaded and unpacked migration: C:\Users\chris\AppData\Local\Temp\migrations3772780638\fs-repo-11-to-12.exe (v1.0.2) Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-12-to-13/v1.0.0/fs-repo-12-to-13_v1.0.0_windows-amd64.zip" Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-12-to-13/v1.0.0/fs-repo-12-to-13_v1.0.0_windows-amd64.zip" Error fetching: exceeded number of retries. last error was GET https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-12-to-13/v1.0.0/fs-repo-12-to-13_v1.0.0_windows-amd64.zip error: 504 Gateway Timeout:

About IPFS Install IPFS

        504 Gateway timeout

            The gateway is taking too long to fetch your content. This could be due to several reasons:

The CID does not exist in the IPFS network

The host that contains the CID has gone offline, is on a slow network connection or overloaded

            You might try waiting for a while and trying again. To prevent having this problem in the future,
            why not self-host a node? You will be able to get all the content in the IPFS network straight
            from its source! For more information see
            the
                implementations page. You
            might also want to have a look at the
            IPFS
                companion browser extension which
            will allow your browser to seamlessly fetch content from your local node.

How you can proceed:

Verify the URL and try again.

Self-host and run an IPFS client that verifies your data.

Try diagnosing your request with the IPFS diagnostic tools.

Inspect the CID or DAG.

Fetching with IPFS: "fs-repo-12-to-13/v1.0.0/fs-repo-12-to-13_v1.0.0_windows-amd64.zip" Downloaded and unpacked migration: C:\Users\chris\AppData\Local\Temp\migrations3772780638\fs-repo-12-to-13.exe (v1.0.0) Running migration fs-repo-11-to-12 ... => Running: C:\Users\chris\AppData\Local\Temp\migrations3772780638\fs-repo-11-to-12.exe -path=C:\Users\chris.ipfs -verbose=true applying 11-to-12 repo migration locking repo at "C:\Users\chris\.ipfs"

• verifying version is '11'
• loading repo configurations
• starting CIDv1 to raw multihash block migration
• backup file will be written to C:\Users\chris.ipfs\11-to-12-cids.txt
• Adding keys in prefix /blocks to backup file 0 CIDv1 keys added to backup file for /blocks
• Adding keys in prefix /filestore to backup file 0 CIDv1 keys added to backup file for /filestore
• backup file will be read from C:\Users\chris.ipfs\11-to-12-cids.txt 2023-12-03 22:02:25.4975509 +0000 GMT m=+0.115919601: Generic migration worker syncing after 0 objects migrated 2023-12-03 22:02:25.4975509 +0000 GMT m=+0.115919601: Generic migration worker syncing after 0 objects migrated 0 CidV1s swapped to multihashes updated version file Running migration fs-repo-12-to-13 ... => Running: C:\Users\chris\AppData\Local\Temp\migrations3772780638\fs-repo-12-to-13.exe -path=C:\Users\chris.ipfs -verbose=true applying 12-to-13 repo migration locking repo at "C:\Users\chris\.ipfs"
• verifying version is '12'

  Upgrading config to new format Swarm.ConnMgr settings are different than the old defaults, skipping updated version file Migration 12 to 13 succeeded Running migration fs-repo-13-to-14 ... => Running: C:\Users\chris\AppData\Local\Temp\migrations3772780638\fs-repo-13-to-14.exe -path=C:\Users\chris.ipfs -verbose=true applying 13-to-14 repo migration locking repo at "C:\Users\chris\.ipfs"

• verifying version is '13'

  Upgrading config to new format updated version file Migration 13 to 14 succeeded Running migration fs-repo-14-to-15 ... => Running: C:\Users\chris\AppData\Local\Temp\migrations3772780638\fs-repo-14-to-15.exe -path=C:\Users\chris.ipfs -verbose=true applying 14-to-15 repo migration locking repo at "C:\Users\chris\.ipfs"

• verifying version is '14'

  Upgrading config to new format updated version file Migration 14 to 15 succeeded Success: fs-repo migrated to version 15. 2023-12-03T22:02:26.493Z FATAL core:constructor node/groups.go:133 The 'Swarm.EnableAutoRelay' config field was removed.Use the 'Swarm.RelayClient.Enabled' instead.

[welcome[bot]]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[whizzzkid]

Thanks for submitting this issue @sisygoboom, can you please attach additional logs that can be found here. Also, I am seeing multiple errors in the message, can you try formatting the error message that showed up?

• 2023-12-03T22:02:26.493Z FATAL core:constructor node/groups.go:133 The 'Swarm.EnableAutoRelay' config field was removed.Use the 'Swarm.RelayClient.Enabled' instead.
• https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-12-to-13/v1.0.0/fs-repo-12-to-13_v1.0.0_windows-amd64.zip error: 504 Gateway Timeout:

At first it looks like the update failed, but then there is the Swarm.EnableAutoRelay error. More info would be nice.

[github-actions[bot]]

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

[github-actions[bot]]

This issue was closed because it is missing author input.