<p>I think the problem is with version 1.5  of dogecoin.I used
rpcpassword=DLKKWE93203909238dkkKKeowxmIOw0232lsakwL02k</p>

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

CC BY-SA 3.0
2014-02-25T18:56:23.553Z
thanks for the suggestion! i won't be able to try this til i get home for the night, but do you think my issue is that the password i'm trying is too short (not 43 chars) or that what i was using for a password that included an underscore?
Jon B
CC BY-SA 3.0
2014-02-25T19:30:21.327Z
@JonBest: Dogecoin checks for a weak password (here's the code: https://github.com/dogecoin/dogecoin/commit/af853674bb7b275355d4ae847d4869e3f73cd246). It estimates the number of bits of entropy by taking the log base 2 of the number of unique characters, and multiplying that by the length of the password. If the number of entropy bits is less than 64, then the password is considered "weak" and is rejected.
Greg Hewgill
CC BY-SA 3.0
2014-02-25T20:04:26.930Z
@JonBest yes, your issue is that rpcpassword. its supposed to be a long mix of upper case, lowercase and numbers. It was just added in a latter release of dogecoin 1.5 which included checkpoints and stronger rpcpassword for much security wow. lol, anyways, i was also confused by it when I compiled it, but I understood it after I tried long password. What greg said is exactly true.
awaisharoon
CC BY-SA 3.0
2014-02-26T00:20:45.017Z
thanks for the specifics! makes sense now...can't wait to correct this this afternoon (;
Jon B
CC BY-SA 3.0
2014-02-26T05:04:14.640Z
wow! much thanks! i do a 42 character long [a-zA-Z0-9] password and it worked. thanks so much @GregHewgill and @ user2185284 !
Jon B
CC BY-SA 3.0
2014-02-25T05:56:59.730Z
2014-02-26T13:16:20.933Z
2014-02-26T13:16:20.933Z
awaisharoon
<p>It's unclear which version of dogecoind you are using. However, in the current 1.5 code on Github, there is a similar message:</p>

<pre><code>if (mapArgs["-rpcuser"] == "" &amp;&amp; mapArgs["-rpcpassword"] == "")
    throw runtime_error(strprintf(
        _("You must set rpcpassword=&lt;password&gt; in the configuration file:\n%s\n"
          "If the file does not exist, create it with owner-readable-only file permissions."),
            GetConfigFile().string().c_str()));
</code></pre>

<p><a href="https://github.com/dogecoin/dogecoin/blob/master-1.5/src/bitcoinrpc.cpp#L1080" rel="nofollow">https://github.com/dogecoin/dogecoin/blob/master-1.5/src/bitcoinrpc.cpp#L1080</a></p>

<p>This indicates that your attempt at working around the problem with <code>chmod 777</code> would not have had the desired effect. Instead, try <code>chmod 600 dogecoin.conf</code>.</p>

CC BY-SA 3.0
2014-02-20T07:10:56.927Z
i tried chmod 600 and that didn't work either...even when i give the parameters in the CLI i get the same thing
Jon B
CC BY-SA 3.0
2014-02-19T23:23:44.997Z
2014-02-19T23:23:44.997Z
Greg Hewgill
<p>Dogecoin does not use port number 8334 the port for dogecoin is 22555 and if the above mentioned is really your password please change it to something more strong </p>

CC BY-SA 3.0
2014-02-20T04:09:47.277Z
def not my real pw lol i'm gonna try what you and greg said shortly
Jon B
CC BY-SA 3.0
2014-02-20T07:08:56.607Z
changing the port didn't work
Jon B
CC BY-SA 3.0
2014-02-21T10:14:42.083Z
change your conf file with the follwoing 
server=1
daemon=1
rpcuser=yourusername
rpcpassword=yourpassword
after saving restart dogecoind
Khan Shahrukh
CC BY-SA 3.0
2014-02-20T02:04:40.223Z
2014-02-20T02:04:40.223Z
Khan Shahrukh
<p>Dogecoin is pretty much a vanilla Bitcoin client with a few tweaks. I noticed I got this same error if there were any syntax errors in my config file. In my case, I had a &quot;parameter-value&quot; instead of &quot;parameter=value&quot;.</p>

CC BY-SA 4.0
2021-07-05T06:47:40.870Z
2021-07-05T06:47:40.870Z
Mr. T
<p>Your password is too short, make it longer and it should work.</p>

CC BY-SA 3.0
2014-02-20T07:09:14.327Z
that's not the real pw, but i did try a much longer password that didn't work either
Jon B
CC BY-SA 3.0
2014-02-20T05:57:57.127Z
2014-02-20T05:57:57.127Z
user13672
<p>I'm having issues starting dogecoind after compiling in ubuntu 12.04 x64 running in VirtualBox on win 7 ultimate x64</p>

<p>here's what i've tried from inside dogecoin/src after <code>make -f makefile.unix</code>:</p>

<pre><code>sudo su
./dogecoind -server -listen -daemon -rpcuser=dogerpc -rpcpassword=dogerpcpw -rpctimeout=30 -rpcport=8334 -rpcallowip=192.168.1.* -rpcallowip=127.0.0.1 -testnet
</code></pre>

<p>and i get:</p>

<pre><code>Error: To use the "-server" option, you must set a secure rpcpassword in the configuration file:
/root/.dogecoin/dogecoin.conf
</code></pre>

<p>so i do:</p>

<pre><code>cd ~/.dogecoin
emacs dogecoin.conf
</code></pre>

<p>i save the following parameters:</p>

<pre><code>rpcuser=dogerpc
rpcpassword=dogerpcpw
rpcport=8334
rpcallowip=192.168.1.*
rpcallowip=127.0.0.1
server=1
daemon=1
listen=1
testnet=1
</code></pre>

<p>i even <code>chmod 777 dogecoin.conf</code> to be sure everyone on God's green earth could access it so that wouldn't be a problem, but still the same error when trying to start up <code>dogecoind</code></p>

<p>would much appreciate any help/tips!</p>

CC BY-SA 3.0
2014-02-19T22:08:40.927Z
This is not Bitcoin related, and you shouldn't be running random daemons as root. It's likely a capitalization error, with this sort of crap it usually is case related.
user13413
CC BY-SA 3.0
2014-02-19T22:11:29.190Z
although SUPER helpful, i'm running a secure dev env so i can run as whatever user i seem fit.  furthermore, the daemon is a derivative of the bitcoin daemon so the question is still relevant. not to mention that according to SO meta, bitcoin.se is for all cryptocurrency related qa. thanks for playing tho
Jon B
CC BY-SA 3.0
2014-02-19T22:14:06.613Z
"Secure dev environment" and "running every process as root" are incompatible statements, you have have one or the other. My comment is actually quite relevant, a lot of scamcoins have has issues with some systems being case sensitive and others not being.
user13413
CC BY-SA 3.0
2014-02-23T09:11:39.017Z
@goatse: According to [community discussion](http://meta.bitcoin.stackexchange.com/a/337) questions about altcoins are on topic.
Murch
<ubuntu><dogecoin><daemon>
dogecoind won't read conf
Jon B
# dogecoind won't read conf

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

I'm having issues starting dogecoind after compiling in ubuntu 12.04 x64 running in VirtualBox on win 7 ultimate x64
here's what i've tried from inside dogecoin/src after make -f makefile.unix:
sudo su
./dogecoind -server -listen -daemon -rpcuser=dogerpc -rpcpassword=dogerpcpw -rpctimeout=30 -rpcport=8334 -rpcallowip=192.168.1.* -rpcallowip=127.0.0.1 -testnet

and i get:
Error: To use the "-server" option, you must set a secure rpcpassword in the configuration file:
/root/.dogecoin/dogecoin.conf

so i do:
cd ~/.dogecoin
emacs dogecoin.conf

i save the following parameters:
rpcuser=dogerpc
rpcpassword=dogerpcpw
rpcport=8334
rpcallowip=192.168.1.*
rpcallowip=127.0.0.1
server=1
daemon=1
listen=1
testnet=1

i even chmod 777 dogecoin.conf to be sure everyone on God's green earth could access it so that wouldn't be a problem, but still the same error when trying to start up dogecoind
would much appreciate any help/tips!

**Tags:** ubuntu, dogecoin, daemon

> **Comments:**
> **username_1**: This is not Bitcoin related, and you shouldn't be running random daemons as root. It's likely a capitalization error, with this sort of crap it usually is case related.  
> **username_0**: although SUPER helpful, i'm running a secure dev env so i can run as whatever user i seem fit.  furthermore, the daemon is a derivative of the bitcoin daemon so the question is still relevant. not to mention that according to SO meta, bitcoin.se is for all cryptocurrency related qa. thanks for playing tho  
> **username_1**: "Secure dev environment" and "running every process as root" are incompatible statements, you have have one or the other. My comment is actually quite relevant, a lot of scamcoins have has issues with some systems being case sensitive and others not being.  
> **username_2**: @goatse: According to [community discussion](http://meta.bitcoin.stackexchange.com/a/337) questions about altcoins are on topic.  

---

## 5 answers

### Answer by username_3 on 2014-02-25. Score: 0 | Accepted answer

I think the problem is with version 1.5 of dogecoin.I used
rpcpassword=DLKKWE93203909238dkkKKeowxmIOw0232lsakwL02k

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

> **Comments:**
> **username_0**: thanks for the suggestion! i won't be able to try this til i get home for the night, but do you think my issue is that the password i'm trying is too short (not 43 chars) or that what i was using for a password that included an underscore?  
> **username_4**: @JonBest: Dogecoin checks for a weak password (here's the code: https://github.com/dogecoin/dogecoin/commit/af853674bb7b275355d4ae847d4869e3f73cd246). It estimates the number of bits of entropy by taking the log base 2 of the number of unique characters, and multiplying that by the length of the password. If the number of entropy bits is less than 64, then the password is considered "weak" and is rejected.  
> **username_3**: @JonBest yes, your issue is that rpcpassword. its supposed to be a long mix of upper case, lowercase and numbers. It was just added in a latter release of dogecoin 1.5 which included checkpoints and stronger rpcpassword for much security wow. lol, anyways, i was also confused by it when I compiled it, but I understood it after I tried long password. What greg said is exactly true.  
> **username_0**: thanks for the specifics! makes sense now...can't wait to correct this this afternoon (;  
> **username_0**: wow! much thanks! i do a 42 character long [a-zA-Z0-9] password and it worked. thanks so much @GregHewgill and @ user2185284 !  

---

### Answer by username_4 on 2014-02-19. Score: 2

It's unclear which version of dogecoind you are using. However, in the current 1.5 code on Github, there is a similar message:
if (mapArgs["-rpcuser"] == "" && mapArgs["-rpcpassword"] == "")
    throw runtime_error(strprintf(
        _("You must set rpcpassword= in the configuration file:\n%s\n"
          "If the file does not exist, create it with owner-readable-only file permissions."),
            GetConfigFile().string().c_str()));

https://github.com/dogecoin/dogecoin/blob/master-1.5/src/bitcoinrpc.cpp#L1080
This indicates that your attempt at working around the problem with chmod 777 would not have had the desired effect. Instead, try chmod 600 dogecoin.conf.

> **Comments:**
> **username_0**: i tried chmod 600 and that didn't work either...even when i give the parameters in the CLI i get the same thing  

---

### Answer by username_5 on 2014-02-20. Score: 0

Dogecoin does not use port number 8334 the port for dogecoin is 22555 and if the above mentioned is really your password please change it to something more strong

> **Comments:**
> **username_0**: def not my real pw lol i'm gonna try what you and greg said shortly  
> **username_0**: changing the port didn't work  
> **username_5**: change your conf file with the follwoing  server=1 daemon=1 rpcuser=yourusername rpcpassword=yourpassword after saving restart dogecoind  

---

### Answer by username_6 on 2021-07-05. Score: 0

Dogecoin is pretty much a vanilla Bitcoin client with a few tweaks. I noticed I got this same error if there were any syntax errors in my config file. In my case, I had a "parameter-value" instead of "parameter=value".


---

### Answer by username_7 on 2014-02-20. Score: -2

Your password is too short, make it longer and it should work.

> **Comments:**
> **username_0**: that's not the real pw, but i did try a much longer password that didn't work either  

---

