I need help getting Litecoin Core running in Ubuntu 24.04.1

Technical Support
1

I have Litecoin Core Installed and I am attempting to start the litecoind -daemon.

I am unsure what directory the litecoin.conf should be installed in. I have it installed into the Litecoin Data directory as follows: /home/ltc/.litecoin. This is the directory that all of the litecoin data is stored such as the blocks, wallet, etc.

Here is what my Litecoin.conf file looks like. I edited out the user name and password.

rpcuser=username
rpcpassword=password
rpcport=2300
daemon=1
server=1
gen=1

I then start the litecoind - daemon and I let it run for a minute and then issue the following command litecoin-cli getinfo as shown below:

Litecoin-Cli Getinfo
Litecoin-Cli Getinfo1920×1080 273 KB

I then get the message cannot connect to the server. Make sure litecoind server is running and that you are connected to the correct RPC Port.

I tried running litecoind -daemon -datadir=/home/ltc/.litecoin/ with no success. I get the same results.

I tried running litecoind -daemon with every option in the conf file with the exception of Gen=1 with no success. I still get the same results.

What am I doing wrong and how can I fix it. Thanks Again for any assistance.

16 Likes
2

I manage to figure out the problem and got it running.

8 Likes
3

What was the solution, might be useful for anyone else experiencing the issue.

12 Likes
4

I am also interested in knowing how to run LTC core on Ubuntu.

11 Likes
6

In what OS do plan to do that?

1 Like
7

— Your litecoin.conf location (/home/ltc/.litecoin/) is correct—that’s the default data directory. Your config file looks properly formatted, but ensure permissions are secure (chmod 600). If litecoin-cli getinfo fails, try:

  1. Wait longer – The daemon may need time to initialize.
  2. Check logs – Run tail -f ~/.litecoin/debug.log for errors.
  3. Verify RPC connection – Use litecoin-cli -rpcport=2300 getinfo to match your config.
  4. Test basic commands – litecoin-cli help confirms CLI functionality.

If issues persist, share the debug.log output for further help. Good luck!

Let me know if you’d like any refinements!