But the strange thing is that I can access suddenly now, I have not changed any settings, can you please try to use ipfs swarm to connect to my node， It should ok if i can get access to my uploaded file /ip4/127.0.0.1/tcp/4001/p2p/12D3KooWLpKz3tdEehMGPX42HPeSL4deyU6uMv4WbVHD2dgXbMqm",
“/ip4/127.0.0.1/udp/4001/quic/p2p/12D3KooWLpKz3tdEehMGPX42HPeSL4deyU6uMv4WbVHD2dgXbMqm”,
“/ip4/192.168.10.101/tcp/4001/p2p/12D3KooWLpKz3tdEehMGPX42HPeSL4deyU6uMv4WbVHD2dgXbMqm”,
“/ip4/192.168.10.101/udp/4001/quic/p2p/12D3KooWLpKz3tdEehMGPX42HPeSL4deyU6uMv4WbVHD2dgXbMqm”,
“/ip4/88.217.185.150/tcp/64583/p2p/12D3KooWLpKz3tdEehMGPX42HPeSL4deyU6uMv4WbVHD2dgXbMqm”,
“/ip4/88.217.185.150/udp/36354/quic/p2p/12D3KooWLpKz3tdEehMGPX42HPeSL4deyU6uMv4WbVHD2dgXbMqm”,
“/ip4/88.217.185.150/udp/64583/quic/p2p/12D3KooWLpKz3tdEehMGPX42HPeSL4deyU6uMv4WbVHD2dgXbMqm”,
“/ip6/::1/tcp/4001/p2p/12D3KooWLpKz3tdEehMGPX42HPeSL4deyU6uMv4WbVHD2dgXbMqm”,
"/ip6/::1/udp/4001/quic/p2p/12D3KooWLpKz3tdEehMGPX42HPeSL4deyU6uMv4WbVHD2dgXbMqm
the case that cannot access to the file can be solved sometimes by restart node, but sometimes didnt work
or someone could check if config is all right or need change
{
“API”: {
“HTTPHeaders”: {}
},
“Addresses”: {
“API”: “/ip4/127.0.0.1/tcp/0”,
“Announce”: [],
“Gateway”: “/ip4/127.0.0.1/tcp/0”,
“NoAnnounce”: [],
“Swarm”: [
“/ip4/127.0.0.1/tcp/0”
]
},
“AutoNAT”: {},
“Bootstrap”: [],
“Datastore”: {
“BloomFilterSize”: 0,
“GCPeriod”: “1h”,
“HashOnRead”: false,
“Spec”: {
“child”: {
“path”: “badgerds”,
“syncWrites”: false,
“truncate”: true,
“type”: “badgerds”
},
“prefix”: “badger.datastore”,
“type”: “measure”
},
“StorageGCWatermark”: 90,
“StorageMax”: “10GB”
},
“Discovery”: {
“MDNS”: {
“Enabled”: Ture,
“Interval”: 10
}
},
“Experimental”: {
“FilestoreEnabled”: false,
“GraphsyncEnabled”: false,
“Libp2pStreamMounting”: false,
“P2pHttpProxy”: false,
“ShardingEnabled”: false,
“StrategicProviding”: false,
“UrlstoreEnabled”: false
},
“Gateway”: {
“APICommands”: [],
“HTTPHeaders”: {
“Access-Control-Allow-Headers”: [
“X-Requested-With”,
“Range”,
“User-Agent”
],
“Access-Control-Allow-Methods”: [
“GET”
],
“Access-Control-Allow-Origin”: [
“*”
]
},
“NoDNSLink”: false,
“NoFetch”: false,
“PathPrefixes”: [],
“PublicGateways”: null,
“RootRedirect”: “”,
“Writable”: false
},
“Identity”: {
“PeerID”: “12D3KooWLpKz3tdEehMGPX42HPeSL4deyU6uMv4WbVHD2dgXbMqm”
},
“Ipns”: {
“RecordLifetime”: “”,
“RepublishPeriod”: “”,
“ResolveCacheSize”: 128
},
“Mounts”: {
“FuseAllowOther”: false,
“IPFS”: “/ipfs”,
“IPNS”: “/ipns”
},
“Peering”: {
“Peers”: null
},
“Pinning”: {
“RemoteServices”: {}
},
“Plugins”: {
“Plugins”: null
},
“Provider”: {
“Strategy”: “”
},
“Pubsub”: {
“DisableSigning”: false,
“Router”: “”
},
“Reprovider”: {
“Interval”: “12h”,
“Strategy”: “all”
},
“Routing”: {
“Type”: “dht”
},
“Swarm”: {
“AddrFilters”: null,
“ConnMgr”: {
“GracePeriod”: “300s”,
“HighWater”: 300,
“LowWater”: 50,
“Type”: “basic”
},
“DisableBandwidthMetrics”: false,
“DisableNatPortMap”: true,
“EnableAutoRelay”: false,
“EnableRelayHop”: false,
“Transports”: {
“Multiplexers”: {},
“Network”: {},
“Security”: {}
}
}
}
try with false…
Another question is that the Sometimes the file can be accessed and sometimes not ，and IPFS DOCs shows : A common issue for new users running IPFS, especially on home networks, is that their IPFS node is sitting behind a NAT (network address translation). It’s common for people who run an IPFS node on their home network to have very long wait times or a high rate of request failure. This is because the rest of the nodes on the IPFS network have difficulty connecting to them through their NAT. The NAT allows many machines to share a single public address, and it is essential for the continued functioning of the IPv4 protocol, which would otherwise be unable to serve the needs of the modern networked population with its 32-bit address space.
I kinda got lost in this conversation. Were you ever able to resolve your problem?
I’m having the same problem. I load something into ipfs desktop app but then I can’t access it from other devices or gateways.