Ubuntu 18.04下Lisk安装失败求助：两种方式均遇异常

Hey there, let's break down these two issues you're facing with Lisk installation on Ubuntu and walk through practical fixes step by step:

Issue 1: "cannot GET /" when accessing http://localhost:7000 (Binary Testnet Installation) #

First off, this error is actually pretty common with Lisk Core's binary installation—here's why and how to fix it:

• Lisk Core (the node itself) doesn't include a built-in web UI. The root path (/) doesn't serve any content because it's an API-only service designed to handle programmatic requests, not browser-based web pages.
• To verify your node is running correctly, test the API directly with a tool like curl or Postman:

  curl http://localhost:7000/api/v3/node/info
  

  If you get a JSON response with node details, your Lisk node is working as expected.
• If you need a web interface to interact with the node, you'll need to install Lisk Hub (the official desktop/mobile wallet) separately, which connects to your local node via the API.
• Double-check the node is running: If you installed it as a system service, run systemctl status lisk-core to confirm it's active. For manual installations, use ps aux | grep lisk to see if the process is running.

Issue 2: "-ERR wrong number of arguments for 'get' command" on http://localhost:6380 (GitHub Source Installation) #

This error is a dead giveaway that you're accessing a Redis server instead of the Lisk API. Here's what's happening and how to fix it:

• Port 6380 is typically used for Redis (the default is 6379, but it looks like your setup uses 6380). Lisk Core relies on Redis for caching, but you shouldn't access Redis directly via a browser—it speaks its own protocol, not HTTP, hence the error.
• Find the correct Lisk API port: Navigate to your Lisk configuration file (usually config/testnet/config.json in the source repo) and look for the api.port field. The default is 7000, so try accessing http://localhost:7000/api/v3/node/info instead.
• Verify Redis compatibility: If Lisk is having trouble connecting to Redis, check:
  1. Is Redis running? Use redis-cli -p 6380 ping—you should get a PONG response.
  2. Does your Lisk config match Redis's port? In config/testnet/config.json, check the redis.port value to ensure it's set to 6380 (or whatever Redis is using).
• Confirm the Lisk node is running: Check the logs in the logs/ directory of your source repo for any startup errors that might prevent the API from listening on the correct port.

General Troubleshooting Tips #

• Check logs first: Binary installations store logs in /var/log/lisk-core/, while source installations log to the logs/ folder. Logs will tell you if the node failed to start, couldn't connect to dependencies, or has configuration issues.
• Firewall rules: Make sure Ubuntu's ufw firewall allows traffic on your Lisk API port (e.g., sudo ufw allow 7000/tcp).
• Dependency versions: For source installations, ensure you're using the exact Node.js and Redis versions specified in Lisk's documentation—mismatched versions can cause unexpected issues.

内容的提问来源于stack exchange，提问作者qCazelles