Common Issues
This page covers the most common problems you might encounter while using Salud and how to resolve them.Backend Connection Issues
”Cannot connect to backend”
Symptoms:- Unable to connect wallet
- Records not loading
- Error messages about API connection
-
Verify backend is running
The backend should be running on
http://localhost:3001 -
Check environment configuration
Verify
frontend/.envhas the correct API URL: -
Check for port conflicts
Make sure no other application is using port 3001:
- Verify firewall settings Ensure your firewall isn’t blocking localhost connections on port 3001
Wallet & Authentication Issues
”Invalid private key”
Common causes:- Private key doesn’t start with
APrivateKey1... - Private key is not exactly 59 characters long
- Extra spaces or characters in the key
-
Verify key format
- Must start with
APrivateKey1 - Must be exactly 59 characters
- No spaces or line breaks
- Must start with
-
Re-export from wallet
- Export private key again from Leo Wallet or Shield Wallet
- Copy the entire key carefully
-
Generate a new key
- Use the “Generate New” button in the Salud connect screen
- Save the generated key securely
Wallet connection drops
If your session disconnects:- Sessions are temporary and stored in memory
- Refreshing the page requires reconnecting
- Your private key is never permanently stored for security
Record Management Issues
”Failed to create record”
Common causes:- Insufficient testnet credits
- Backend errors
- Network connectivity issues
-
Check your balance
- View wallet balance in the app
- Request testnet credits from Aleo faucet if needed
-
Enable Demo Mode
For testing without blockchain transactions, set in
backend/.env:In demo mode:- All features work normally
- Records stored in localStorage
- No real blockchain transactions
- Records won’t persist across browsers/devices
- Check backend logs Look at the backend console for detailed error messages
Records not appearing
Symptoms:- Created records don’t show up
- Record list is empty
-
Wait for blockchain sync
- Records are fetched from blockchain on connect
- Initial sync may take 10-15 seconds
- Check browser console for sync status
-
Refresh the connection
- Disconnect and reconnect your wallet
- This triggers a fresh sync from blockchain
-
Verify record creation
- Check backend logs to confirm record was created
- Look for transaction confirmation messages
QR Code & Sharing Issues
QR code not scanning
Solutions:- Ensure good lighting when scanning
- Try zooming in/out on the QR code
- Use a different QR scanner app
- Manually copy the access token instead
Access token not working
Check:- Token hasn’t expired (check access duration)
- Doctor’s address is correct
- Token was copied completely without extra characters
Transaction Failures
Transactions timing out
Possible causes:- Network congestion on Aleo testnet
- Backend connection issues
- Insufficient credits
- Wait a few minutes and try again
- Check your wallet balance
- Verify backend is connected to Aleo network
- Check
ALEO_API_URLin backend.env:
“Insufficient credits” error
Solutions:- Request testnet credits from Aleo faucet
- Use Demo Mode for testing
- Check balance using the wallet info in the app
Development Issues
Frontend won’t start
Solutions:-
Reinstall dependencies
-
Check Node.js version
Requires Node.js 18 or higher:
-
Verify .env file
Make sure
frontend/.envexists with:
Backend crashes or errors
Solutions:-
Check environment variables
Verify
backend/.envis configured: -
Reinstall dependencies
- Check logs Look for specific error messages in the backend console output
Still Having Issues?
If you’re still experiencing problems:- Check existing issues on GitHub to see if others have reported the same problem
- Create a new issue with:
- Detailed description of the problem
- Steps to reproduce
- Error messages (if any)
- Your environment (OS, Node.js version, browser)
- Join the Aleo community Discord for general questions about the Aleo blockchain
Next Steps
FAQ
Frequently asked questions
Support
Get help from the community