# Why am i getting this error whenever i try to start ipfs **URL:** \ **Category:** Uncategorized\ **Created:** [March 30, 2023, 4:21pm UTC](https://discuss.ipfs.tech/t/why-am-i-getting-this-error-whenever-i-try-to-start-ipfs/16211 "2023-03-30T16:21:38Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Sho](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@Sho](https://discuss.ipfs.tech/u/Sho)\ **Post date:** [March 30, 2023, 4:21pm UTC](https://discuss.ipfs.tech/t/why-am-i-getting-this-error-whenever-i-try-to-start-ipfs/16211/1 "2023-03-30T16:21:38Z")
PS C:\Users\Kepha\shorts\> ipfs daemon Initializing daemon… Kubo version: 0.18.1 Repo version: 13 System version: amd64/windows Golang version: go1.19.1 Computing default go-libp2p Resource Manager limits based on: - ‘Swarm.ResourceMgr.MaxMemory’: “3.2 GB” - ‘Swarm.ResourceMgr.MaxFileDescriptors’: 4611686… Applying any user-supplied overrides on top. Run ‘ipfs swarm limit all’ to see the resulting limits. Swarm listening on /ip4/127.0.0.1/tcp/4001 Swarm listening on /ip4/127.0.0.1/udp/4001/quic Swarm listening on /ip4/127.0.0.1/udp/4001/quic-v1 Swarm listening on /ip4/127.0.0.1/udp/4001/quic-v1/webtransport/certhash/uEiCA6n9p8Yt-o1UPon3pX9omyeB7wyy5BfhOaql\_tCUqrg/certhash/uEiB6RiDoQvJJb6JJ3gXbb27imcq-\_o9H8mzDVzvwWA\_vbw Swarm listening on /ip4/169.254.14.29/tcp/4001 Swarm listening on /ip4/169.254.14.29/udp/4001/quic Swarm listening on /ip4/169.254.14.29/udp/4001/quic-v1 Swarm listening on /ip4/169.254.14.29/udp/4001/quic-v1/webtransport/certhash/uEiCA6n9p8Yt-o1UPon3pX9omyeB7wyy5BfhOaql\_tCUqrg/certhash/uEiB6RiDoQvJJb6JJ3gXbb27imcq-\_o9H8mzDVzvwWA\_vbw Swarm listening on /ip4/169.254.244.209/tcp/4001 Swarm listening on /ip4/169.254.244.209/udp/4001/quic Swarm listening on /ip4/169.254.244.209/udp/4001/quic-v1 Swarm listening on /ip4/169.254.244.209/udp/4001/quic-v1/webtransport/certhash/uEiCA6n9p8Yt-o1UPon3pX9omyeB7wyy5BfhOaql\_tCUqrg/certhash/uEiB6RiDoQvJJb6JJ3gXbb27imcq-\_o9H8mzDVzvwWA\_vbw Swarm listening on /ip4/172.26.176.1/tcp/4001 Swarm listening on /ip4/172.26.176.1/udp/4001/quic Swarm listening on /ip4/172.26.176.1/udp/4001/quic-v1 Swarm listening on /ip4/172.26.176.1/udp/4001/quic-v1/webtransport/certhash/uEiCA6n9p8Yt-o1UPon3pX9omyeB7wyy5BfhOaql\_tCUqrg/certhash/uEiB6RiDoQvJJb6JJ3gXbb27imcq-\_o9H8mzDVzvwWA\_vbw Swarm listening on /ip4/192.168.124.95/tcp/4001 Swarm listening on /ip4/192.168.124.95/udp/4001/quic Swarm listening on /ip4/192.168.124.95/udp/4001/quic-v1 Swarm listening on /ip4/192.168.124.95/udp/4001/quic-v1/webtransport/certhash/uEiCA6n9p8Yt-o1UPon3pX9omyeB7wyy5BfhOaql\_tCUqrg/certhash/uEiB6RiDoQvJJb6JJ3gXbb27imcq-\_o9H8mzDVzvwWA\_vbw Swarm listening on /ip6/::1/tcp/4001 Swarm listening on /ip6/::1/udp/4001/quic Swarm listening on /ip6/::1/udp/4001/quic-v1 Swarm listening on /ip6/::1/udp/4001/quic-v1/webtransport/certhash/uEiCA6n9p8Yt-o1UPon3pX9omyeB7wyy5BfhOaql\_tCUqrg/certhash/uEiB6RiDoQvJJb6JJ3gXbb27imcq-\_o9H8mzDVzvwWA\_vbw Swarm listening on /p2p-circuit Swarm announcing /ip4/127.0.0.1/tcp/4001 Swarm announcing /ip4/127.0.0.1/udp/4001/quic Swarm announcing /ip4/127.0.0.1/udp/4001/quic-v1 Swarm announcing /ip4/127.0.0.1/udp/4001/quic-v1/webtransport/certhash/uEiCA6n9p8Yt-o1UPon3pX9omyeB7wyy5BfhOaql\_tCUqrg/certhash/uEiB6RiDoQvJJb6JJ3gXbb27imcq-\_o9H8mzDVzvwWA\_vbw Swarm announcing /ip4/192.168.124.95/tcp/4001 Swarm announcing /ip4/192.168.124.95/udp/4001/quic Swarm announcing /ip4/192.168.124.95/udp/4001/quic-v1 Swarm announcing /ip4/192.168.124.95/udp/4001/quic-v1/webtransport/certhash/uEiCA6n9p8Yt-o1UPon3pX9omyeB7wyy5BfhOaql\_tCUqrg/certhash/uEiB6RiD\_o9H8mzDVzvwWA\_vbw Swarm announcing /ip6/::1/tcp/4001 Swarm announcing /ip6/::1/udp/4001/quic Swarm announcing /ip6/::1/udp/4001/quic-v1 Swarm announcing /ip6/::1/udp/4001/quic-v1/webtransport/certhash/uEiCA6n9p8Yt-o1UPon3pX9omyeB7wyy5BfhOaql\_tCUqrg/certhash/uEiB6RiDoQvJJb Error: serveHTTPApi: invalid API address: “[https://ip4/127.0.0.1/tcp/5001](https://ip4/127.0.0.1/tcp/5001)” (err: failed to parse multiaddr “[https://ip4/127.0.0.1/tcp/5001](https://ip4/127.0.0.1/tcp/5001)”: must begin with /) ---
**Author:** ![Jorropo](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/jorropo/32/3230_2.png) [@Jorropo](https://discuss.ipfs.tech/u/Jorropo)\ **Post date:** [March 30, 2023, 4:25pm UTC](https://discuss.ipfs.tech/t/why-am-i-getting-this-error-whenever-i-try-to-start-ipfs/16211/2 "2023-03-30T16:25:14Z")
Your configured API should be a multiaddr so `/ip4/127.0.0.1/tcp/5001`. ---
**Author:** ![Sho](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@Sho](https://discuss.ipfs.tech/u/Sho)\ **Post date:** [March 30, 2023, 4:27pm UTC](https://discuss.ipfs.tech/t/why-am-i-getting-this-error-whenever-i-try-to-start-ipfs/16211/3 "2023-03-30T16:27:54Z")
how can i fix it i cant access the desktop app to config the app says that the app has shutdown ---
**Author:** ![Jorropo](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/jorropo/32/3230_2.png) [@Jorropo](https://discuss.ipfs.tech/u/Jorropo)\ **Post date:** [March 30, 2023, 4:29pm UTC](https://discuss.ipfs.tech/t/why-am-i-getting-this-error-whenever-i-try-to-start-ipfs/16211/4 "2023-03-30T16:29:41Z")
You need to edit the `config.json` file, you can find your install path here: > **[Move an IPFS installation | IPFS Docs](https://docs.ipfs.tech/how-to/move-ipfs-installation/move-ipfs-installation/#ipfs-desktop)** > > This page walks through how to move your IPFS installation from one system to another. This process is cross-platform compatible and is especially useful for readers who are changing operating systems. However, the process is different for CLI and... You don’t want to move your instalation, but this will tell you where `.ipfs` is stored, then you need to open `config` file and change the `API` field to `/ip4/127.0.0.1/tcp/5001`. ---
**Author:** ![Sho](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@Sho](https://discuss.ipfs.tech/u/Sho)\ **Post date:** [March 30, 2023, 4:38pm UTC](https://discuss.ipfs.tech/t/why-am-i-getting-this-error-whenever-i-try-to-start-ipfs/16211/5 "2023-03-30T16:38:00Z")
I dont have the option for Move Repository Location because the app does show on the notfication bar on my windows , when i open the app it opens and shows error and when i close it it goes ---
**Author:** ![Sho](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@Sho](https://discuss.ipfs.tech/u/Sho)\ **Post date:** [March 30, 2023, 4:38pm UTC](https://discuss.ipfs.tech/t/why-am-i-getting-this-error-whenever-i-try-to-start-ipfs/16211/6 "2023-03-30T16:38:41Z")
isnt there the option of moving **Move Repository Location**.using vs ---
**Author:** ![sevenrats](https://avatars.discourse-cdn.com/v4/letter/s/7ea924/32.png) [@sevenrats](https://discuss.ipfs.tech/u/sevenrats)\ **Post date:** [March 30, 2023, 6:11pm UTC](https://discuss.ipfs.tech/t/why-am-i-getting-this-error-whenever-i-try-to-start-ipfs/16211/7 "2023-03-30T18:11:13Z")
did you get this sorted? The solution is to change the text of your .ipfs/config file, not to press any buttons in the app. ---
**Author:** ![Sho](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@Sho](https://discuss.ipfs.tech/u/Sho)\ **Post date:** [March 31, 2023, 10:23am UTC](https://discuss.ipfs.tech/t/why-am-i-getting-this-error-whenever-i-try-to-start-ipfs/16211/8 "2023-03-31T10:23:17Z")
it was solved now why do i get error in con sole fetch.browser.js:104 POST [http://localhost:5001/api/v0/add?stream-channels=true&progress=false](http://localhost:5001/api/v0/add?stream-channels=true&progress=false) net::ERR\_CONNECTION\_RESET fetchWith @ fetch.browser.js:104 fetch @ http.js:140 Client.fetch @ core.js:205 post @ http.js:188 (anonymous) @ add-all.js:36 await in (anonymous) (async) last @ index.ts:8 add @ add.js:22 handleUpload @ Upload.js:47 callCallback @ react-dom.development.js:4164 invokeGuardedCallbackDev @ react-dom.development.js:4213 invokeGuardedCallback @ react-dom.development.js:4277 invokeGuardedCallbackAndCatchFirstError @ react-dom.development.js:4291 executeDispatch @ react-dom.development.js:9041 processDispatchQueueItemsInOrder @ react-dom.development.js:9073 processDispatchQueue @ react-dom.development.js:9086 dispatchEventsForPlugins @ react-dom.development.js:9097 (anonymous) @ react-dom.development.js:9288 batchedUpdates$1 @ react-dom.development.js:26140 batchedUpdates @ react-dom.development.js:3991 dispatchEventForPluginEventSystem @ react-dom.development.js:9287 dispatchEventWithEnableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay @ react-dom.development.js:6465 dispatchEvent @ react-dom.development.js:6457 dispatchDiscreteEvent @ react-dom.development.js:6430 react\_devtools\_backend.js:2655 TypeError: Failed to fetch at fetchWith (fetch.browser.js:104:1) at Client.fetch (http.js:140:1) at Client.fetch (core.js:205:1) at Client.post (http.js:188:1) at add-all.js:36:1 at async last (index.ts:8:1) at async Object.add (add.js:22:1) at async handleUpload (Upload.js:47:1)