Latest posts of: xtpu

Show Posts
Pages: [1]

on: May 22, 2014, 03:12:35 PM

Have definitely tracked it down to a firewall issue. As soon as I disable the firewall, it connects fine, but what should the correct firewall rules be? Currently, I have my OUTPUT policy set to ACCEPT (less risky, easier to work with). In my input policy I have the following rule: Code: -A INPUT -p tcp --dport 8333 I know that I typed UDP before, but I actually meant TCP.

on: May 22, 2014, 04:24:09 AM

I'm running bitcoind on a remote server (so I can only use the "headless" version). However, the client is not connecting to the bitcoin network. The "getinfo" command shows "connections: 0". Here's what my bitcoin.conf looks like: Code: daemon=1 server=1 rpcuser=<redacted> rpcpassword=<redacted> rpcport=<redacted> rpctimeout=60 Port 8333 is open for UDP traffic in my firewall and I have used an external port scanner to verify that it is open. However, I understand that that's not actually necessary for outgoing connections. I've also checked that my date / time is synchronized (this was suggested in some of the threads that I found on this topic). What are other possibilities? Edited to Add: This a Debian setup. Most things Ubuntu should apply as well.

on: March 10, 2014, 08:01:42 PM

Trade is pending with user "tagged"

on: March 03, 2014, 08:40:46 AM

I'm looking to buy 3 BTC paying with USPS money order. As this is my first transaction on Bitcoin Talk, I am prepared to send the money order to you first, and you can send me BTC after you have cashed / deposited it. Because of this, you must have a good reputation! I would prefer a regular seller. I would also be prepared to work with a reputable escrow. The BitStamp rate seems to be the most widely used, that I have seen, but if this rate is for some reason unacceptable to you, make me an offer. I'm mostly looking to buy because I'm curious about Bitcoin, so I don't mind being flexible with the exchange rate (within reason). Thanks! Trade is pending with user "tagged"

on: February 10, 2014, 09:24:18 AM

For some reason, the major BTC exchanges don't accept postal money orders. Can anybody recommend a reputable exchange or a reputable private seller that will accept a USPS money order?

on: January 05, 2014, 11:52:37 PM

I'm looking for a hosting company that offers Linux dedicated servers and that is friendly to hosting gambling websites. The company needs to be able to accept bitcoin for payment. Preferably, I would like someone who has been in business for a while and has reviews. Let me know if there are any additional specifics needed, but I think that pretty much covers it. I did try googling before asking, but there are not very many threads / hosting companies that discuss specifically gambling. Thank you.

on: January 04, 2014, 06:17:42 AM

I'm developing a web application that would not only accept, but also send payments to web users. For now, I'm using the official client (bitcoind), but I suddenly became worried about this issue: The wallet is encrypted. So to send a payment, I need to run walletpassphrase. However, as far as I understand from the documentation, when I unlock the wallet, it becomes unlocked not just for one connection or one transaction, but for all connections / transactions. This means that if I do "walletpassphrase", "send", "walletlock", there is a small window of time when the wallet is unlocked. If someone then has access to the machine, they might be able to send a malicious transaction in that window of time without knowing the passphrase. It would make much more sense if I provided the wallet password per-transaction. I.e. "send <wallet password> <normal send parameters>". Then, the malicious user would have to have the wallet password in order to perform the attack. Is something like this possible with the official client? If not, can anybody recommend a client for this purpose? Or would I have to modify the source code? Has anybody come up with solutions for this that don't involve using an external service? I see that quite a few people run gambling services with bitcoin... maybe one of them could chime in to tell us how they do it?

on: January 04, 2014, 12:29:45 AM

I don't think I understand, isn't that what is done by these lines in the bitcoin.conf? Code: rpcuser=some_user rpcpassword=some_password

on: January 03, 2014, 11:29:55 PM

I did a web search before posting, but none of the similar topics shed any light on my problem. This is the command I'm using to start bitcoind: Code: ./bin/32/bitcoind -datadir=/somedir -daemon This is the contents of my bitcoin.conf, which is located in /somedir (of course): Code: server=1 rpcuser=some_user rpcpassword=some_password rpcport=8332 rpctimeout=60 Here are the results of netstat --ip -lpan \| grep bitcoin Code: tcp 0 0 127.0.0.1:8332 0.0.0.0:* LISTEN 24203/bitcoind tcp 0 0 0.0.0.0:8333 0.0.0.0:* LISTEN 24203/bitcoind Then I attempt to send a commend to the bitcoind using: Code: ./bin/32/bitcoind -datadir=/somedir getinfo Result Code: error: couldn't connect to server I'm probably missing something simple and obvious, but what?

Pages: [1]