If after scanning the admin's pairing code at the machine it proceeds to the "Sorry, we're down" screen, it means we should focus our attention to server-side settings.
This is most often caused by one or more of the following:
- Unsupported ticker source
- Incorrect wallet setup
- Stopped server process
Before trying the below, reboot your machine to ensure that it continues to land on the 'Sorry, we're down' screen upon boot.
Bitstamp's ticker only supports USD and EUR. Log in to the Lamassu web admin and in the price panel select one of the three other tickers, such as BitPay, which support most currencies.
If this was the source of the error, the machine should proceed to the Hello screen. For good measure, within the server's command line, run the following two commands individually to restart the backend:
stop lamassu-server restart lamassu-admin && start lamassu-server LAMASSU_ENV=debug
Incorrect wallet setup
The machine may go to 'Sorry, we're down' if you're using incorrect wallet credentials.
If using BitGo:
Follow the steps under the 'Checking for success' section of our configuring Bitgo article. Avoid the common pitfalls described and check the log files for any error messages relating to BitGo.
Pulling server logs
After addressing the above, you'll want to pull server logs to check if there are any persistent errors.
Specifically, you'll want to look for any log entries containing the word 'ERROR', including any messages from the wallet module, ticker, or exchange integration (optional). Also, check for periodic 'poll requests', as these indicate that your machine is connected successfully to the local network and communicating with your server.
To do so, run the commands indicated on our 'Checking server logs' article.
If the above does not resolve the issue, it may be due to the network blocking communication between the machine and backend over port 3000.
See our article for network requirements and best practices for connectivity.