Cannot remote to regtest node with curl cmd - Empty reply from server Hi I'm new to rpc curl cmds and having some issues connecting to my regtest node.  I'm getting &quot;empty reply from server&quot; which makes me think it is connecting but something is misconfigured.
Looking through various threads here I found similar things but nothing that quite fit the bill, but apologies if this is something that has already been covered.
bitcoin.conf settings
# Options only for regtest
[regtest]
# datadir
datadir=/mnt/mydisk/regtest
# Listen for incoming connections on non-default port.(default: 8333 or testnet: 18333)
port=18444
# RPC allow all IPS (shouldn't have this on mainnet)
rpcallowip=0.0.0.0/0
# RPC bind IP
#rpcbind=192.168.86.30
# RPC port(default:8332 or testnet:18332)
rpcport=18443

my curl cmd returns
curl: (52) Empty reply from server

curl cmd
 curl --user xxxuser:xxxcookie --data-binary '{&quot;jsonrpc&quot;: &quot;1.0&quot;, &quot;id&quot;:&quot;curltest&quot;, &quot;method&quot;: &quot;getblockcount&quot;, &quot;params&quot;: [] }' -H 'content-type: text/plain;'  http://192.168.86.30:18444/

I'm also seeing this in the debug.log but not sure what it means or how to fix
UPnP: ExternalIPAddress = XX.XXX.XX.XXX
AddLocal(XX.XXX.XX.XXX:18444,3)
AddPortMapping(18444, 18444, 192.168.86.30) failed with code 718 (ConflictInMappingEntry)
UPNP_DeletePortMapping() returned: 606


Also worth noting I have another regtest node and the 2 nodes are connected without issue.
Any help appreciated.
You are defining RPC port 18443 and attempting to connect to 18444 in your example.
There's no situation where you should attempt to rpcallowip to anything but localhost, don't get used to doing that or making systems which require it. There is no situation in which this is safe to do, even regtest can cause damage to your system.