# Taurus node connection problems **URL:** \ **Category:** Support\ **Created:** [February 11, 2025, 3:19pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698 "2025-02-11T15:19:05Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Alexander\_Zamesov](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/alexander_zamesov/32/860_2.png) [@Alexander\_Zamesov](https://forum.autonomys.xyz/u/Alexander_Zamesov)\ **Post date:** [February 11, 2025, 3:19pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/1 "2025-02-11T15:19:05Z")
## Issue Report ### Environment Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-131-generic x86\_64 Taurus Node 28 Jan ### Problem Hi! I have a problem with node start - no peers (wait fo several hours) 😩 Ports are open and checked by nc command
 Mainnet node works fine on 30333 and 30433 on second unit. Please advise. Start script: [Unit] Description=Subspace Node After=network.target [Service] User=root Type=simple ExecStart=subspace-node run –chain taurus –name Inoutik –base-path /sub/node –farmer –listen-on /ip4/0.0.0.0/tcp/31333 –dsn-listen-on /ip4/0.0.0.0/tcp/31433 –blocks-pruning archive-canonical –state-pruning archive-canonical –sync full – –domain-id 0 –blocks-pruning archive-canonical –state-pruning 16000 Restart=on-failure LimitNOFILE=65535 [Install] WantedBy=multi-user.target [Logs.txt](https://forum.autonomys.xyz/uploads/short-url/eLs2BEubmXZEXUURvKzO3Fn5S29.txt) (7.0 KB) ---
**Author:** ![Randy-Autonomys](https://avatars.discourse-cdn.com/v4/letter/r/0ea827/32.png) [@Randy-Autonomys](https://forum.autonomys.xyz/u/Randy-Autonomys)\ **Post date:** [February 11, 2025, 4:14pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/2 "2025-02-11T16:14:17Z")
At first glance it does look like a port forward issue. I know you have verified that they are open, but I would encourage you to double check. In the meantime, can you make sure that you are starting with no data in your /sub/node folder and can verify that you are using the latest Taurus release? > **[Release taurus-2025-jan-28 · autonomys/subspace](https://github.com/autonomys/subspace/releases/tag/taurus-2025-jan-28)** > > Notable changes > > Move capturing Domain trace roots from runtime to client in #3338 > Optimize block finalization in #3347 > Fix cluster piece getter in #3345 > > Build variants > There are two versions of x... ---
**Author:** ![Alexander\_Zamesov](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/alexander_zamesov/32/860_2.png) [@Alexander\_Zamesov](https://forum.autonomys.xyz/u/Alexander_Zamesov)\ **Post date:** [February 11, 2025, 7:23pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/3 "2025-02-11T19:23:42Z")
Double checked and changed for 39333 and 39433 (and test with nc from outside). Also make new directory for node files in root
 and still no peers. Also checked firewalls on node and tried dmz on router for this node. It’s look like some network problem to me, but mainnet node works well on the same lan and router
 PS i use the latest release - version 0.1.0-21fdb9a19dbf58d932c4bf8a3a0b360dcadd7e0e [log.txt](https://forum.autonomys.xyz/uploads/short-url/lmKrBMPWN7Bh7RvDFemqE1Bc0Pi.txt) (4.2 KB) ---
**Author:** ![Randy-Autonomys](https://avatars.discourse-cdn.com/v4/letter/r/0ea827/32.png) [@Randy-Autonomys](https://forum.autonomys.xyz/u/Randy-Autonomys)\ **Post date:** [February 11, 2025, 8:19pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/4 "2025-02-11T20:19:42Z")
I don’t think that there is a problem on the chain side of things as there are over 130 fully synced Taurus nodes. I think you are correct about it being a network issue. For me, that usually means just opening up the ports and forwarding them as well as making sure firewalls are open. Sometimes ISP’s block some ports but you have tried different ones. I think I am going to have to wait for someone else to chime in here. Anyone with zero peers that I have helped was due ports, network issues, or ISP blockages. ---
**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\ **Post date:** [February 13, 2025, 6:51am UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/5 "2025-02-13T06:51:14Z")
Note that options after `--` are for domain, and domain has its own networking configuration like `–listen-on`. You’ll have to forward those ports too and in case of conflicts you may need to customize it as well. See [Port Forwarding & Firewall | Farm from Anywhere](https://docs.autonomys.xyz/farming/guides/port-config) for details and run node with `--help` to see available options (`--help` can be added to both left and right of `--help` to see consensus and domain options accordingly). ---
**Author:** ![Alexander\_Zamesov](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/alexander_zamesov/32/860_2.png) [@Alexander\_Zamesov](https://forum.autonomys.xyz/u/Alexander_Zamesov)\ **Post date:** [February 20, 2025, 5:38pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/6 "2025-02-20T17:38:29Z")
@Randy-Autonomys @nazar-pc it’s definetely something wrong with the taurus node binaries - i started both mainnet and taurus nodes on the same server with the same config - and mainnet node started without any problem and taurus not. Please check logs [taurus.txt](https://forum.autonomys.xyz/uploads/short-url/rSX3eaoDZxxEFfGhESVvSr2iq0I.txt) (8.4 KB) ---
**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\ **Post date:** [February 20, 2025, 5:51pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/7 "2025-02-20T17:51:35Z")
According to original message you have customized DSN port to `31433`, but logs indicate that you did not. Make sure you reloaded service config. I can personally also recommend using Docker instead of systemd, which is much easier to configure and to update. ---
**Author:** ![Alexander\_Zamesov](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/alexander_zamesov/32/860_2.png) [@Alexander\_Zamesov](https://forum.autonomys.xyz/u/Alexander_Zamesov)\ **Post date:** [February 20, 2025, 6:32pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/8 "2025-02-20T18:32:00Z")
I changed port of course before starting the nodes. They use the same ports, the same config and the same server. I also deleted node files folder for both nodes. Mainnet finded external address and peers right away, but taurus didnt. So problem not in ports or network - its in binaries or network itself. Check fresh logs. Here is start comand for mainnet node [Unit] Description=Subspace Node After=network.target [Service] User=root Type=simple ExecStart=/usr/local/bin/subspace-node run --chain mainnet --name Inoutik\_Cluster --base-path /sub/node\_m --sync full --farmer --listen-on /ip4/0.0.0.0/tcp/30333 Restart=on-failure LimitNOFILE=65535 [Install] WantedBy=multi-user.target And here - for taurus: GNU nano 7.2 /etc/systemd/system/subspaced-node-taurus.service [Unit] Description=Subspace Node After=network.target [Service] User=root Type=simple ExecStart=/usr/local/bin/subspace-node-taurus run --chain taurus --name Inoutik\_Cluster --base-path /sub/node\_t --sync full --farmer --listen-on /ip4/0.0.0.0/tcp/30333 Restart=on-failure LimitNOFILE=65535 [Install] WantedBy=multi-user.target [taurus2.txt](https://forum.autonomys.xyz/uploads/short-url/5j4rd2popuE6LjZ38q36L8ibYye.txt) (10.6 KB) ---
**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\ **Post date:** [February 20, 2025, 6:44pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/9 "2025-02-20T18:44:34Z")
You can’t run the two different nodes with the same port on the same server! It will 100% cause hard to diagnose issues just like you see, which is why it was suggested to change the ports to make sure they do not overlap between Mainnet and Taurus nodes. Better yet, use Docker, it’ll fail to bind to the same port twice (at least by default with setup described in the documentation), helping you to correct configuration sooner. ---
**Author:** ![Alexander\_Zamesov](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/alexander_zamesov/32/860_2.png) [@Alexander\_Zamesov](https://forum.autonomys.xyz/u/Alexander_Zamesov)\ **Post date:** [February 20, 2025, 7:16pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/10 "2025-02-20T19:16:25Z")
I’m not running two nodes đŸ«  - i stopped mainnet before starting taurus. I used the same ports to be sure that ports are open and works. ![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/b/bb7420b7ee82351bf43d7908f2471ee3702597ef.png) Im sure it will not help but where i can get docker files for taurus node for check? here only mainnet - [Install | Farm from Anywhere](https://docs.autonomys.xyz/farming/cli/install) Also i changed ports many times, its not the issue ---
**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\ **Post date:** [February 20, 2025, 7:30pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/11 "2025-02-20T19:30:01Z")
Container images have the same name, just use `taurus-whatever` as the tag, which always corresponds to the release you want to use. The latest right now is `taurus-2025-jan-28`. Your logs above only include a few seconds after start, so not clear what issue you’re having if any. ---
**Author:** ![Alexander\_Zamesov](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/alexander_zamesov/32/860_2.png) [@Alexander\_Zamesov](https://forum.autonomys.xyz/u/Alexander_Zamesov)\ **Post date:** [February 20, 2025, 9:19pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/12 "2025-02-20T21:19:36Z")
well as expected - no changes. Mainnet works perfect, taurus - not [docker mainnet.txt](https://forum.autonomys.xyz/uploads/short-url/vwWaRj1DRtHXpzZYd19WDHbD5AY.txt) (18.4 KB) [docker - taurus.txt](https://forum.autonomys.xyz/uploads/short-url/4dQVc7ziP5EsO3gKQxxPag9LHcf.txt) (11.8 KB) ---
**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\ **Post date:** [February 20, 2025, 9:31pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/13 "2025-02-20T21:31:27Z")
@ved or @ning could you take a look at this, please? It seems to indicate potential issues with infra. I am not running Taurus nodes myself though. ---
**Author:** ![ved](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/ved/32/693_2.png) [@ved](https://forum.autonomys.xyz/u/ved)\ **Post date:** [February 21, 2025, 9:44am UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/14 "2025-02-21T09:44:10Z")
@Alexander_Zamesov I have run a node on taurus from the scratch This is the compose file I have used ```auto services: node: image: ghcr.io/autonomys/node:taurus-2025-jan-28 volumes: - ~/Subspace/taurus/node:/var/subspace:rw ports: - "0.0.0.0:30333:30333/tcp" - "0.0.0.0:30433:30433/tcp" restart: unless-stopped command: [ "run", "--chain", "taurus", "--base-path", "/var/subspace", "--listen-on", "/ip4/0.0.0.0/tcp/30333", "--dsn-listen-on", "/ip4/0.0.0.0/tcp/30433", "--rpc-listen-on", "0.0.0.0:9944", "--rpc-cors", "all", "--rpc-methods", "unsafe", "--farmer", "--name", "ved_local", ] healthcheck: timeout: 5s interval: 30s retries: 60 ``` I have a atleast 20 peers connected and synced to target block. I have not used systemd yet. Apologies for asking again, have you double checked your firewall to be sure ? ---
**Author:** ![Alexander\_Zamesov](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/alexander_zamesov/32/860_2.png) [@Alexander\_Zamesov](https://forum.autonomys.xyz/u/Alexander_Zamesov)\ **Post date:** [February 22, 2025, 6:42pm UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/15 "2025-02-22T18:42:18Z")
Firewall is not the issue
 i used the same ports for mainnet and for taurus. ---
**Author:** ![Rabinovitch](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/rabinovitch/32/99_2.png) [@Rabinovitch](https://forum.autonomys.xyz/u/Rabinovitch)\ **Post date:** [March 6, 2025, 5:54am UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/16 "2025-03-06T05:54:11Z")
I have the same problem with Taurus node at home. Though it works absolutely fine at work. And yes, I know how to forward ports - mainnet node is running at home just fine. When my systemd unit looks like this (I call it “default config”, though the ports are not default): ```auto Description=Subspace Operator Node in Taurus testnet After=network.target [Service] Type=simple User=rabinovitch ExecStart=/home/rabinovitch/subspace-taurus/subspace-node-ubuntu-x86_64-skylake-taurus-2025-march-05 run \ --chain taurus \ --name RabinovitchTaurusOperator \ --base-path /home/rabinovitch/subspace-taurus/operator-data \ --blocks-pruning archive-canonical \ --state-pruning archive-canonical \ --listen-on /ip4/0.0.0.0/tcp/34719 \ --dsn-listen-on /ip4/0.0.0.0/tcp/45317 \ --sync full \ -- \ --domain-id 0 \ --listen-on /ip4/0.0.0.0/tcp/41226 \ --blocks-pruning archive-canonical \ --state-pruning 16000 Restart=on-failure RestartSec=7 LimitNOFILE=1024000 [Install] WantedBy=multi-user.target ``` I don’t see any external address, or any traffic at all. Please see the [Taurus\_default\_config.txt](https://forum.autonomys.xyz/uploads/short-url/gZquNjtNTY5p4Ah0HSHh94rwzHb.txt) (9.9 KB) But when I use bootstrap node by @vexr: ```auto --bootstrap-node /dns/bootstrap-0.evm.taurus.ai3.farm/tcp/11205/p2p/12D3KooWDpPPWd7htCiSFaJq5WJPuX1iksBYZBCjnoeRberCmag6 ``` The log looks different, I see `Discovered new external address` lines (each time with different port for some reason!) and some traffic, 0.1kiB/s - 0.3kiB/s: [Taurus\_vexr\_bootstrap.txt](https://forum.autonomys.xyz/uploads/short-url/3ZgCiig5nqRvM7IIoH37JflcMKY.txt) (11.2 KB) But the node still doesn’t synchronize, no matter how much time I give it and no matter how many times I restart it. Some screenshots: ![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/2/2cbd4c056c990981466d577ece0c7ccd975704f1.png) ![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/1/1b0cf36c6dc33ca51b3988704b5d0fb904dd9b0a.png) ![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/3/3e9f7c42b7210744d7689f454d14671afdb589bb.png) ---
**Author:** ![Rabinovitch](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/rabinovitch/32/99_2.png) [@Rabinovitch](https://forum.autonomys.xyz/u/Rabinovitch)\ **Post date:** [March 6, 2025, 5:58am UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/17 "2025-03-06T05:58:47Z")
CPU: AMD Ryzen 7 3700X 8-Core Processor, bare metal PC, NVME drive for operator-data. 300 Mbit/s Internet channel. ---
**Author:** ![Jim-Autonomys](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/jim-autonomys/32/2922_2.png) [@Jim-Autonomys](https://forum.autonomys.xyz/u/Jim-Autonomys)\ **Post date:** [March 6, 2025, 9:29am UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/18 "2025-03-06T09:29:46Z")
That’s interesting! So could it possibly be that your ISP has blocked Taurus bootstrap nodes but not mainnet ones? This could also explain OP’s problem too. Can you both run these commands please? ```auto nslookup bootstrap-0.taurus.subspace.network nslookup bootstrap-1.taurus.subspace.network ``` Could you also see if you can access port 30333 on these machines and then vexr’s bootstrap node to see if there is a difference. ---
**Author:** ![Rabinovitch](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/rabinovitch/32/99_2.png) [@Rabinovitch](https://forum.autonomys.xyz/u/Rabinovitch)\ **Post date:** [March 6, 2025, 9:55am UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/19 "2025-03-06T09:55:55Z")
```auto Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: bootstrap-0.taurus.subspace.network Address: 65.108.232.56 rabinovitch@filecoin-miner:~$ nslookup bootstrap-1.taurus.subspace.network Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: bootstrap-1.taurus.subspace.network Address: 65.108.71.22 ``` > Could you also see if you can access port 30333 on these machines Sorry, I’m not sure how to do it. In my network 30333 if forwarded to another PC where the mainnet node is running. ---
**Author:** ![Jim-Autonomys](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/jim-autonomys/32/2922_2.png) [@Jim-Autonomys](https://forum.autonomys.xyz/u/Jim-Autonomys)\ **Post date:** [March 6, 2025, 10:20am UTC](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698/20 "2025-03-06T10:20:54Z")
> [@Rabinovitch](#): > > Sorry, I’m not sure how to do it. In my network 30333 if forwarded to another PC where the mainnet node is running. I mean access 30333 on the bootstrap nodes. You could use `telnet` to see if you get a connection refused or not. ```auto telnet bootstrap-0.taurus.subspace.network 30333 telnet bootstrap-1.taurus.subspace.network 30333 ``` I see output like this: ```auto Trying 65.108.232.56... Connected to bootstrap-0.taurus.subspace.network. Escape character is '^]'. ``` [Next page](https://forum.autonomys.xyz/t/taurus-node-connection-problems/4698.md?page=2)