Hi I have an instance on google cloud which I installed IPFS on it. my issue is when I run it only announce local ip and internal ip in swarm list and can’t detect external (floating) IP. How can announce external IP?

I don’t know. I have a node behind NAT and after few minutes it adds correctly the exterior IP (if the ports are accessible) to the announce. No idea about the mechanism behind it, but it is automatic (in my case) after some time.

You can announce external IPs that IPFS is unable to infer by specifying them in the config. Specifically, the Addresses.Announce section. For example, if you wanted to announce 1.2.3.4 on port 4001 (assuming you’re using the default swarm port), you would specify it as shown below. "Announce": [ …

Good Day all. I have added these lines to the config file but either they are not being used when the daemon starts or I am looking in the wrong place for verification. x’s inserted in this post to block who knows what. “Addresses”: { “API”: “/ip4/127.0.0.1/tcp/5001”, “Announce”: [ “/ip4/69.15.x…

[image] buddy: Specifically it still shows Swarm listening on /ip4/12.208.x.xx/tcp/4001 What does it show in the list of Swarm announcing /ipx/x/tcp/x addresses when starting the daemon?

There is no line for swarm announcing or no-announcing.

As far as I can tell, the daemon never recognized the “Announce” and “No-Announce” entries in the config. After a few days, it came up with the correct outside facing ip address. Assuming it just asked around. :slight_smile:

I have noticed when others post the messages issued when the daemon starts, that there is a line for “Announce”. Thinking it gets that from the config file. Maybe I hit that void between being syntactically correct, so the daemon starts, but still not being recognized.

According to the documentation the syntax should be right. ipfs/go-ipfs/blob/master/docs/config.md # The go-ipfs config file The go-ipfs config file is a JSON document located at `$IPFS_PATH/config`. It is read once at node instantiation, either for an offline command, or when starting the…

Whatever is put on Announce should become what is announced. If that does not happen, you are not editing the right config that is being used by the daemon (i.e. you are editing the config for your local user but run ipfs as root), or your config is mangled in a way that it is still parseable but d…

How to add external IP to IPFS swarm announcing list

Uncategorized

RubenKelevra February 26, 2020, 7:19pm 8

@stebalien is this a known bug? You mentioned that behavoir in the other thread, but not the Announce/NoAnnounce configuration.

Topic		Replies	Views
IPFS, NAT and k8s Help go-ipfs , kubernetes	6	2468	August 14, 2020
IPFS Configuration :: Funny NAT Issue(s) When Using Append Announce Help	2	279	May 20, 2023
Auto discovery with multiple docker networks: only one network is listed in "swarm addrs local" Networking go-ipfs	10	1094	November 12, 2020
Address for swarm connect is not using port 4001 Help go-ipfs	5	919	January 30, 2020
Help find out why discovery takes so long Help go-ipfs	4	474	April 26, 2021

How to add external IP to IPFS swarm announcing list

Related topics