# Gavin Andresen
# 2010-11-01 17:05:43
# https://bitcointalk.org/index.php?topic=1624.msg19567#msg19567

If bitcoin thinks the connection is not allowed, then it just ignores the connection attempt@p{--} nothing is written to debug.log.  That's probably the right thing to do@p{--} otherwise somebody malicious could try to fill up your hard disk by repeatedly attempting to connect to port 8332. @p{par}

If you can recompile bitcoind, the "ClientAllowed" routine in rpc.cpp is where a printf() to log connections could go.  But I'd guess either you misspelled "rpcallowip" (I always type rcp instead of rpc...) or have a firewall blocking connections. @p{par}

If you can ssh into the web server machine (or any other machine, actually), try: @p{brk}
  curl @s{(link)} @p{par}

If you get "couldn't connect to host" then it is a firewall problem. @p{brk}
If you get "Empty reply from server" then it is an rpcallowip problem. @p{brk}
If you get an HTTP "Authorization Required" or "Authorization Failed" reply, then it is a username/password mismatch (those ARE logged in debug.log, though@p{--} grep for ThreadRPC). @p{brk}