How to view the logs

<aside> 💡 If you're having installation issues these commands might not be useful for you. please read the daemon installation issues paragraph below

</aside>

Watch the logs with wisp tail For full logs type wisp logs If all else fails journalctl -u wisp | tail

Container install log location: /var/lib/wisp/daemon/config/servers/*<server uuid>*/install.log Daemon install log: /var/log/wisp-install.log NPM log: /var/lib/wisp/daemon/npm_install.log

Enabling debug mode

Debug mode is useful for various issues. To enable it, you need to edit the wisp.yaml and reboot the daemon with wisp restart. In /var/lib/wisp/daemon/config/wisp.yaml set logger.level to debug. After this is done, restart wisp.

logger:
  level: debug

Daemon installation issues

If things really aren't working as expected these logs might help:

• Node never gets added to the panel
• Node is not responding in the panel

Daemon won't start

Refer to the wisp logs if the daemon is failing to start. Here are some common errors you might get while wisp is trying to startup:

• Error while attempting to fetch updated Egg file (HTTP/404)
• npm install exited with code 1

The server failed to install

• If you're getting a server failing to install, you can check the container install logs.

The server won't start

If a server isn't starting you should check the wisp logs for any errors.

• A common issue is "failed to bind port"

View all available guides, chat with the WISP community on Discord and open a support ticket should you require assistance.