Title: rpc connection from armory failing authentication Post by: PeterTheGrape on April 14, 2017, 12:45:17 AM Thanks, one more question. I looked at my debug log file, about 12 megabytes, and it is almost entirely
"2017-04-13 11:15:12 ThreadRPCServer incorrect password attempt from 127.0.0.1:51582 2017-04-13 11:15:13 ThreadRPCServer incorrect password attempt from 127.0.0.1:51585 2017-04-13 11:15:14 ThreadRPCServer incorrect password attempt from 127.0.0.1:51588 2017-04-13 11:15:15 ThreadRPCServer incorrect password attempt from 127.0.0.1:51591 2017-04-13 11:15:16 ThreadRPCServer incorrect password attempt from 127.0.0.1:51594 2017-04-13 11:15:17 ThreadRPCServer incorrect password attempt from 127.0.0.1:51597 2017-04-13 11:15:18 ThreadRPCServer incorrect password attempt from 127.0.0.1:51600 2017-04-13 11:15:19 ThreadRPCServer incorrect password attempt from 127.0.0.1:51603 2017-04-13 11:15:20 ThreadRPCServer incorrect password attempt from 127.0.0.1:51606 2017-04-13 11:15:22 ThreadRPCServer incorrect password attempt from 127.0.0.1:51609 2017-04-13 11:15:23 ThreadRPCServer incorrect password attempt from 127.0.0.1:51612 2017-04-13 11:15:24 ThreadRPCServer incorrect password attempt from 127.0.0.1:51615 2017-04-13 11:15:25 ThreadRPCServer incorrect password attempt from 127.0.0.1:51618 2017-04-13 11:15:26 ThreadRPCServer incorrect password attempt from 127.0.0.1:51621 2017-04-13 11:15:27 ThreadRPCServer incorrect password attempt from 127.0.0.1:51625 2017-04-13 11:15:27 ThreadRPCServer incorrect password attempt from 127.0.0.1:51626 2017-04-13 11:15:28 ThreadRPCServer incorrect password attempt from 127.0.0.1:51629 2017-04-13 11:15:28 ThreadRPCServer incorrect password attempt from 127.0.0.1:51631 2017-04-13 11:15:29 ThreadRPCServer incorrect password attempt from 127.0.0.1:51634 2017-04-13 11:15:29 ThreadRPCServer incorrect password attempt from 127.0.0.1:51635 2017-04-13 11:15:30 ThreadRPCServer incorrect password attempt from 127.0.0.1:51637 2017-04-13 11:15:30 ThreadRPCServer incorrect password attempt from 127.0.0.1:51639 2017-04-13 11:15:31 ThreadRPCServer incorrect password attempt from 127.0.0.1:51641 2017-04-13 11:15:31 ThreadRPCServer incorrect password attempt from 127.0.0.1:51643 2017-04-13 11:15:32 ThreadRPCServer incorrect password attempt from 127.0.0.1:51646 2017-04-13 11:15:32 ThreadRPCServer incorrect password attempt from 127.0.0.1:51647 2017-04-13 11:15:33 ThreadRPCServer incorrect password attempt from 127.0.0.1:51650 2017-04-13 11:15:33 ThreadRPCServer incorrect password attempt from 127.0.0.1:51651 2017-04-13 11:15:34 ThreadRPCServer incorrect password attempt from 127.0.0.1:51653 2017-04-13 11:15:34 ThreadRPCServer incorrect password attempt from 127.0.0.1:51655 2017-04-13 11:15:35 ThreadRPCServer incorrect password attempt from 127.0.0.1:51657 2017-04-13 11:15:35 ThreadRPCServer incorrect password attempt from 127.0.0.1:51659 2017-04-13 11:15:36 ThreadRPCServer incorrect password attempt from 127.0.0.1:51661 2017-04-13 11:15:36 ThreadRPCServer incorrect password attempt from 127.0.0.1:51663 2017-04-13 11:15:37 ThreadRPCServer incorrect password attempt from 127.0.0.1:51665 2017-04-13 11:15:37 ThreadRPCServer incorrect password attempt from 127.0.0.1:51667 2017-04-13 11:15:38 ThreadRPCServer incorrect password attempt from 127.0.0.1:51669 2017-04-13 11:15:38 ThreadRPCServer incorrect password attempt from 127.0.0.1:51671 2017-04-13 11:15:39 ThreadRPCServer incorrect password attempt from 127.0.0.1:51673 2017-04-13 11:15:39 ThreadRPCServer incorrect password attempt from 127.0.0.1:51675 2017-04-13 11:15:40 ThreadRPCServer incorrect password attempt from 127.0.0.1:51677 2017-04-13 11:15:40 ThreadRPCServer incorrect password attempt from 127.0.0.1:51679 2017-04-13 11:15:41 ThreadRPCServer incorrect password attempt from 127.0.0.1:51681 2017-04-13 11:15:41 ThreadRPCServer incorrect password attempt from 127.0.0.1:51683 2017-04-13 11:15:42 ThreadRPCServer incorrect password attempt from 127.0.0.1:51685 2017-04-13 11:15:42 ThreadRPCServer incorrect password attempt from 127.0.0.1:51687 2017-04-13 11:15:43 ThreadRPCServer incorrect password attempt from 127.0.0.1:51689 2017-04-13 11:15:43 ThreadRPCServer incorrect password attempt from 127.0.0.1:51691 2017-04-13 11:15:44 ThreadRPCServer incorrect password attempt from 127.0.0.1:51693 2017-04-13 11:15:44 ThreadRPCServer incorrect password attempt from 127.0.0.1:51695 2017-04-13 11:15:45 ThreadRPCServer incorrect password attempt from 127.0.0.1:51697 2017-04-13 11:15:45 ThreadRPCServer incorrect password attempt from 127.0.0.1:51699 2017-04-13 11:15:46 ThreadRPCServer incorrect password attempt from 127.0.0.1:51701 2017-04-13 11:15:46 ThreadRPCServer incorrect password attempt from 127.0.0.1:51703 2017-04-13 11:15:47 ThreadRPCServer incorrect password attempt from 127.0.0.1:51705 2017-04-13 11:15:47 ThreadRPCServer incorrect password attempt from 127.0.0.1:51707 2017-04-13 11:15:48 ThreadRPCServer incorrect password attempt from 127.0.0.1:51709 2017-04-13 11:15:48 ThreadRPCServer incorrect password attempt from 127.0.0.1:51711 2017-04-13 11:15:49 ThreadRPCServer incorrect password attempt from 127.0.0.1:51713 2017-04-13 11:15:49 ThreadRPCServer incorrect password attempt from 127.0.0.1:51715 2017-04-13 11:15:50 ThreadRPCServer incorrect password attempt from 127.0.0.1:51717 2017-04-13 11:15:50 ThreadRPCServer incorrect password attempt from 127.0.0.1:51719 2017-04-13 11:15:51 ThreadRPCServer incorrect password attempt from 127.0.0.1:51721 2017-04-13 11:15:51 ThreadRPCServer incorrect password attempt from 127.0.0.1:51723 2017-04-13 11:15:52 ThreadRPCServer incorrect password attempt from 127.0.0.1:51725" on and on, is that normal? Title: rpc connection from armory failing authentication Post by: achow101 on April 14, 2017, 01:13:29 AM That is not normal. Do you have any software on your computer which is supposed to use or try to use Bitcoin Core's JSON-RPC server?
Title: rpc connection from armory failing authentication Post by: PeterTheGrape on April 14, 2017, 02:47:49 AM That is not normal. Do you have any software on your computer which is supposed to use or try to use Bitcoin Core's JSON-RPC server? I'm using Armory. Title: rpc connection from armory failing authentication Post by: achow101 on April 14, 2017, 03:25:53 AM I'm using Armory. If you have rpcuser and rpcpassword set in the bitcoin.conf, remove or comment those out and restart Core.Title: rpc connection from armory failing authentication Post by: PeterTheGrape on April 14, 2017, 03:34:34 AM I'm using Armory. If you have rpcuser and rpcpassword set in the bitcoin.conf, remove or comment those out and restart Core.I only installed bitcoin core because Armory Needs it. I don't do and haven't done anything with bitcoin core. None of the wallets has any coins so no big risk I guess. Title: rpc connection from armory failing authentication Post by: achow101 on April 14, 2017, 03:40:59 AM I only installed bitcoin core because Armory Needs it. I don't do and haven't done anything with bitcoin core. None of the wallets has any coins so no big risk I guess. Check that a .cookie file exists in Bitcoin Core's data directory. If it doesn't, restart Core.I'm going to split this thread and move it to Armory. Title: Re: rpc connection from armory failing authentication Post by: PeterTheGrape on April 14, 2017, 04:50:56 AM I only installed bitcoin core because Armory Needs it. I don't do and haven't done anything with bitcoin core. None of the wallets has any coins so no big risk I guess. Check that a .cookie file exists in Bitcoin Core's data directory. If it doesn't, restart Core.I'm going to split this thread and move it to Armory. Yes, there is a .cookie file, I hadn't noticed that before. I opened it with notepad and it just has __cookie__ followed by about 50 random characters. |