Skip to main content

Reference: Troubleshooting

Use this reference to identify and resolve common communication and deployment issues with WEVA.

Communication Errors​

Status / ErrorProbable CauseCorrective Action
Status: Offline (Red)Controller IP unreachable.Verify physical cabling and ping the controller IP.
Values reading '0'Modbus service disabled on controller.Enable Modbus via WAGO WBM (Web-Based Management).
Socket TimeoutMaximum connections reached.Close other Modbus masters or increase timeout in WDX.

System Logs (Docker)​

Logs are the primary diagnostic tool for the backend services. Use the following commands to inspect the state of the system.

Inspect Backend Logs​

docker logs weva-backend --tail 100 -f

Inspect Database Connectivity​

Verify that the backend can reach the SQL database:

docker exec -it weva-backend ping weva-db

WDX Runtime Diagnostics​

If the WDX interface is inaccessible:

  • Port Conflict: Ensure port 7081 is not being used by another local service (e.g., IIS or another web server).
  • Hung Container: Restart the runtime: 
    docker restart wdx-runtime

Troubleshooting Logs Placeholder Screenshot: Example terminal view showing a successful Modbus polling log entry.

Support Reference​

If issues persist after following these steps, contact WAGO Technical Support with the following information:

  1. Docker container logs (weva-backend).
  2. Screenshots of the WDX Driver Settings.
  3. Controller firmware version.