<p>I think the problem is with version 1.5  of dogecoin.I fixed it by using this long password.</p>

<p>rpcpassword=DLKKWE93203909238dkkKKeowxmIOw0232lsakwL02k</p>

<p>to solve the problem. Change the password to whatever you want, just use lowercase, upper case and letters, it should fix the problem</p>

CC BY-SA 3.0
2014-02-25T06:00:27.530Z
2014-02-25T06:00:27.530Z
awaisharoon
<p>I just compiled dogecoin-qt using the original source, and edited it to generate new genesis block, because i want to create new coin for educational purpose. It is working just fine, and without an error, but whenever i try to crate a conf file in %appdata%\dogecoin\dogecoin.conf with this content</p>

<blockquote>
  <p>rpcuser=abc
  rpcpassword=abcd
  rpcport=22565
  server=1
  daemon=1
  listen=1</p>
</blockquote>

<p>It will say </p>

<blockquote>
  <p>"To use the -server options you must setup a secure rpcpassword in configuration file at xxxxx\Dogecoin\dogecoin.conf rpcuser=xx
  rpcpass=xxxxxxxxx</p>
</blockquote>

<p>this an error that should only appear if i used server=1 in conf file, but dont provide rpcuser and pass. but i am already providing that.</p>

<p>I am looking for someones help to get me to understand what I am doing wrong. And sorry if this doesn't belong here.</p>

CC BY-SA 3.0
2014-02-24T17:21:05.193Z
If you're modifying the source code, then you're programming. Use your debugger and put a breakpoint on the message you get and find out how it got there. We can't really help you because we don't know what you have modified.
Greg Hewgill
CC BY-SA 3.0
2014-02-24T18:26:40.977Z
@GregHewgill 
http://pastebin.com/YnBWT7L1

I ran dogecoin-qt with --debug from cmd, and saved this debug. Please have a look. I see that it says
2014-02-24 18:23:01 Bound to [::]:33465
2014-02-24 18:23:01 Bound to 0.0.0.0:33465

it should write 127.0.0.1, right?
I did not modify code at all, other than changing the genesis block and modifying the total number of coins, coins per block etc.
awaisharoon
CC BY-SA 3.0
2014-02-24T19:12:50.587Z
I don't see a problem with that. Address 0.0.0.0 means it's listening on *all* interfaces, not just 127.0.0.1.
Greg Hewgill
CC BY-SA 3.0
2014-02-24T19:16:00.847Z
@GregHewgill could this be a reason that I mined genesis block by using testnet feature of the coin, then added the genesis block hash and merkle hash to the coin's source code, and compiled again. And that is why the coin has this problem? Because I have heard some problem with bitcoin where if you run bitcoin -testnet. you have to paste the bitcoin.conf to %appdata%\bitcoin\testnet\bitcoin.conf or %appdata%\bitcoin\testnet.conf
could that be an issue?
awaisharoon
CC BY-SA 3.0
2014-02-25T04:32:56.507Z
@GregHewgill thank you for the link of that thread. yes, i have the same issue with dogecoin-qt and dogecoind. on that thread, no one was able to help them out.
awaisharoon
CC BY-SA 3.0
2014-02-25T06:01:45.537Z
@GregHewgill yes, posted my answer to my own question for others help.
awaisharoon
CC BY-SA 3.0
2014-02-25T06:02:42.277Z
@GregHewgill but can you help me to setup dogecoin to use a smaller password like all the other coins like litecoin, feathercoin etc. I want to use a password like rpcpassword=abcd
awaisharoon
CC BY-SA 3.0
2014-02-25T06:50:37.733Z
You're already editing the source code. Change the `weakPassword()` function such that it meets your relaxed complexity requirements.
Greg Hewgill
CC BY-SA 3.0
2014-02-25T07:02:11.760Z
@GregHewgill you have been a great help. Would you answer my other question regarding setting up a node as well?
awaisharoon
<bitcoin-core><dogecoin>
Compiled and modified source wont work with server=1
awaisharoon
# Compiled and modified source wont work with server=1

(Asked by: username_0 on 2014-02-24)

I just compiled dogecoin-qt using the original source, and edited it to generate new genesis block, because i want to create new coin for educational purpose. It is working just fine, and without an error, but whenever i try to crate a conf file in %appdata%\dogecoin\dogecoin.conf with this content

> rpcuser=abc
> rpcpassword=abcd
> rpcport=22565
> server=1
> daemon=1
> listen=1

It will say

> "To use the -server options you must setup a secure rpcpassword in configuration file at xxxxx\Dogecoin\dogecoin.conf rpcuser=xx
> rpcpass=xxxxxxxxx

this an error that should only appear if i used server=1 in conf file, but dont provide rpcuser and pass. but i am already providing that.

I am looking for someones help to get me to understand what I am doing wrong. And sorry if this doesn't belong here.

**Tags:** bitcoin-core, dogecoin

> **Comments:**
> **username_1**: If you're modifying the source code, then you're programming. Use your debugger and put a breakpoint on the message you get and find out how it got there. We can't really help you because we don't know what you have modified.  
> **username_0**: @username_1  http://pastebin.com/YnBWT7L1  I ran dogecoin-qt with --debug from cmd, and saved this debug. Please have a look. I see that it says 2014-02-24 18:23:01 Bound to [::]:33465 2014-02-24 18:23:01 Bound to 0.0.0.0:33465  it should write 127.0.0.1, right? I did not modify code at all, other than changing the genesis block and modifying the total number of coins, coins per block etc.  
> **username_1**: I don't see a problem with that. Address 0.0.0.0 means it's listening on *all* interfaces, not just 127.0.0.1.  
> **username_0**: @username_1 could this be a reason that I mined genesis block by using testnet feature of the coin, then added the genesis block hash and merkle hash to the coin's source code, and compiled again. And that is why the coin has this problem? Because I have heard some problem with bitcoin where if you run bitcoin -testnet. you have to paste the bitcoin.conf to %appdata%\bitcoin\testnet\bitcoin.conf or %appdata%\bitcoin\testnet.conf could that be an issue?  
> **username_0**: @username_1 thank you for the link of that thread. yes, i have the same issue with dogecoin-qt and dogecoind. on that thread, no one was able to help them out.  
> **username_0**: @username_1 yes, posted my answer to my own question for others help.  
> **username_0**: @username_1 but can you help me to setup dogecoin to use a smaller password like all the other coins like litecoin, feathercoin etc. I want to use a password like rpcpassword=abcd  
> **username_1**: You're already editing the source code. Change the `weakPassword()` function such that it meets your relaxed complexity requirements.  
> **username_0**: @username_1 you have been a great help. Would you answer my other question regarding setting up a node as well?  

---

## 1 answers

### Answer by username_0 on 2014-02-25. Score: 0

I think the problem is with version 1.5 of dogecoin.I fixed it by using this long password.

rpcpassword=DLKKWE93203909238dkkKKeowxmIOw0232lsakwL02k

to solve the problem. Change the password to whatever you want, just use lowercase, upper case and letters, it should fix the problem


---

