<p>You need to give them different ports. Refer to <a href="https://en.bitcoin.it/wiki/Running_Bitcoin" rel="nofollow">https://en.bitcoin.it/wiki/Running_Bitcoin</a> on how to listen on different ports.</p>

CC BY-SA 3.0
2014-08-29T12:11:01.007Z
Is it rpcport=8332 in the config file the same as -port=<port> in the command line parameter?
Gregor Walter
CC BY-SA 3.0
2014-08-29T12:35:21.297Z
That's the port that other programs on your server/computer can use to interact with the node. You can also change that port otherwise it will conflict with the other currencies. For the actual Bitcoin network connections you need the `port=XXX` configuration.
Luca Matteis
CC BY-SA 3.0
2014-08-29T12:48:58.743Z
Thank you! https://getaddr.bitnodes.io/ confirms I am running the node on the right port. Will add other currencies now.
Gregor Walter
CC BY-SA 3.0
2014-08-29T11:45:30.227Z
2014-08-29T11:45:30.227Z
Luca Matteis
<p>Most of the different coins already run on different ports so you should be able to run these without problems (other than resource issues if your machine can't handled it).  You may need to just check the default port assignments and vary them.</p>

<p>If you want to run multiple instances of bitcoin for example you need to change ports.</p>

<pre><code>-port=&lt;port&gt;           Listen for connections on &lt;port&gt; (default: 8333 or testnet: 18333)
-rpcport=&lt;port&gt;        Listen for JSON-RPC connections on &lt;port&gt; (default: 8332 or testnet: 18332)
</code></pre>

<p>You will allso need the -noupnp flag to disable upnp so that you can manually nat external ports.</p>

CC BY-SA 3.0
2015-11-03T09:48:41.477Z
2015-11-03T09:48:41.477Z
Louis
<p>simple question. I would like to run several full nodes for Bitcoin, Litecoin, Darkcoin and so on, but don't they run on the same port (8333)? Will this just work or do I need to give them several different ports?</p>

<p>Cheers</p>

CC BY-SA 3.0
2014-08-29T18:55:35.240Z
Note that each of these clients may require a significant amount of memory, so you may have to check whether your machine has enough.  See also http://bitcoin.stackexchange.com/questions/1270/is-it-possible-to-run-more-than-one-client-instance-on-a-machine?rq=1
Nate Eldredge
<bitcoind>
Running Multiple Full Nodes on one Host
Gregor Walter
# Running Multiple Full Nodes on one Host

(Asked by: username_0 on 2014-08-29)

simple question. I would like to run several full nodes for Bitcoin, Litecoin, Darkcoin and so on, but don't they run on the same port (8333)? Will this just work or do I need to give them several different ports?

Cheers

**Tags:** bitcoind

> **Comments:**
> **username_1**: Note that each of these clients may require a significant amount of memory, so you may have to check whether your machine has enough.  See also http://bitcoin.stackexchange.com/questions/1270/is-it-possible-to-run-more-than-one-client-instance-on-a-machine?rq=1  

---

## 2 answers

### Answer by username_2 on 2014-08-29. Score: 4

You need to give them different ports. Refer to <https://en.bitcoin.it/wiki/Running_Bitcoin> on how to listen on different ports.

> **Comments:**
> **username_0**: Is it rpcport=8332 in the config file the same as -port=<port> in the command line parameter?  
> **username_2**: That's the port that other programs on your server/computer can use to interact with the node. You can also change that port otherwise it will conflict with the other currencies. For the actual Bitcoin network connections you need the `port=XXX` configuration.  
> **username_0**: Thank you! https://getaddr.bitnodes.io/ confirms I am running the node on the right port. Will add other currencies now.  

---

### Answer by username_3 on 2015-11-03. Score: 1

Most of the different coins already run on different ports so you should be able to run these without problems (other than resource issues if your machine can't handled it). You may need to just check the default port assignments and vary them.

If you want to run multiple instances of bitcoin for example you need to change ports.

```
-port=<port>           Listen for connections on <port> (default: 8333 or testnet: 18333)
-rpcport=<port>        Listen for JSON-RPC connections on <port> (default: 8332 or testnet: 18332)

```

You will allso need the -noupnp flag to disable upnp so that you can manually nat external ports.


---

