RPCAllowIP problems

[BTCPlay.me]

When I run the server on localhost and connect to it from localhost it works. However when I add in the proper ip and run it from an external server it gives a connection refused.
Bitcoin.conf contents:
server=1
rpcuser=root
rpcpassword=examplepassword
rpcconnect=123.123.123.123
rpcport=8332
rpcalowip=123.123.123.123 (the ip of the external server).
So what am I doing wrong?

[1715339112]

1715339112

[1715339112]

1715339112

[1715339112]

1715339112

[cr1776]

Can you connect to the rpcport remotely at all? Eg with telnet or a port scanner?  This is to eliminate a firewall issue.

[tonytumble]

When I run the server on localhost and connect to it from localhost it works. However when I add in the proper ip and run it from an external server it gives a connection refused.
Bitcoin.conf contents:
server=1
rpcuser=root
rpcpassword=examplepassword
rpcconnect=123.123.123.123
rpcport=8332
rpcalowip=123.123.123.123 (the ip of the external server).
So what am I doing wrong?

seems you are using bitcoind to connect to 123.123.123.123 and send the commands there.
remove rpcconnect=123.123.123.123. only the rpcallowip tells the bitcoind that the host with this ip
is allowed to connect to your bitcoind. the rpcconnect tells bitcoind to connect to that server and send the commands
there...

[Randian Hero]

You may also need to configure your router to forward the port to your computer. The easiest way to do this is usually to look for something about DMZ in your router admin page and enter your computer's local IP... usually it's 192.168.x.x and you can find out buy running ipconfig /all in the command prompt if you're running Windows.

[shorena]

You may also need to configure your router to forward the port to your computer. The easiest way to do this is usually to look for something about DMZ in your router admin page and enter your computer's local IP... usually it's 192.168.x.x and you can find out buy running ipconfig /all in the command prompt if you're running Windows.

WTF? Dont DMZ your entire traffic to a single machine that is not a router/dedicated firewall.

btw tonytumble already solved the issue AFAICT. OP was relaying the RPC requests back to the machine that is sending.