Failed to push command to device

[hlg212]

Hello, I deployed WISP using Docker OpenWISP（docker-openwisp）;
Then, two OpenWRTs were launched using Docker;

WISP and OpenWRT are in different network segments;
wisp : 172.43.0.0/24
openwrt: 172.17.0.0/24

Successfully registered the device to WISP through OpenWISP config in OpenWRT;
Everything seems normal at the current location;

In order to enable WISP to push commands to devices, I modified one of the nodes to vpnclient. The VPN networking was successful, and the address assigned by the VPN was' 10.8.0.4 ';

3: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 02:42:ac:11:00:09 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.9/24 brd 172.17.0.255 scope global br-lan
       valid_lft forever preferred_lft forever
4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 500
    link/none
    inet 10.8.0.4 peer 10.8.0.1/32 scope global tun0
       valid_lft forever preferred_lft forever
7749: eth0@if7750: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP group default
    link/ether 02:42:ac:11:00:09 brd ff:ff:ff:ff:ff:ff link-netnsid 0

After testing, it was found that executing 'ping 10.8.0.4' from vpnserver, celery, and celery_manitoring can all connect;
Handmade 'sh' in a porcelain container [email protected] You can also log in normally;

Then, in the dashboard interface of WISP, I initiated a command to execute 'END COMMAND' on the device. The command was simple: 'ping - c 4 174.17.0.1';
The page 'Recent Commands' does not display the return of the command;
image:

This problem has been bothering me for several days now.
What should I do now? Can you provide me with troubleshooting ideas and solutions?
Thanks

[nemesifier]

Do you never get a reply at all? Even after reloading the page? If so, have you checked the browser console to see if there's any JS error?

Are you using the stable version?

[hlg212]

Do you never get a reply at all? Even after reloading the page? If so, have you checked the browser console to see if there's any JS error?

Are you using the stable version?

I have checked all the containers and found no obvious errors.
There are no JavaScript errors on the page either. The only error in the console—which I believe should not cause any issues—is:
'WebSocket connection to 'wss://api.openwisp.org/ws/notification/' failed:'

The 'SEND COMMAND' did not receive any response. To ensure proper communication, I also tried deploying a client within the same network segment (using the docker-compose configuration below).
The device can successfully register to OpenWISP and can be viewed in the 'Devices' page.
Additionally, the relevant 'template' is pulled to the device (/etc/init.d/openwisp-config restart).

I also checked the 'connection_command' table, which contains the commands sent from the page.
I also examined the 'network' in Redis, where the sent commands are stored, but I'm not sure what to check next.

The 'Health status' of all registered devices shows as 'unknown'. I suspect this is related to the issue, but I'm unsure how to further investigate the logs for this problem.

openWISP Version: 24.11.2
openwisp-controller: 1.1
openwisp-firmware-upgrader: 1.1
openwisp-ipam: 1.1
openwisp-monitoring: 1.1.1
openwisp-network-topology: 1.1.1
openwisp-notifications:1.1
openwisp-radius: 1.1
openwisp-users: 1.1.0
openwisp-utils: 1.1.1
netdiff: 1.1
netjsonconfig: 1.1

---

docker-compose.yaml ('https://github.com/openwisp/docker-openwisp')
docker-compose.yml
.env.txt

[nemesifier]

Can you paste the contents of /etc/config/openwisp and redact sensitive info please?

[nemesifier]

@hlg212 were you able to solve it?

[hlg212]

@hlg212 were you able to solve it?

Yes, I should say it's resolved.
The issue was likely because the code in the Docker latest image wasn't the most recent version.

Here is how I fixed it:
I redeployed the entire Wisp system, and then the device status returned to normal, with the Health status showing as OK.

However, at this point, the 'send command' feature still wasn't working. I noticed an exception in the 'celery' service: 'ash: openwisp_config: not found'.
It originated from /usr/local/lib/python3.12/site-packages/openwisp_controller/connection/connectors/openwrt/ssh.py.

After comparing the code, I found that the Docker image was using version 1.1. Once I overwrote it with the code from version 1.2, the command execution worked properly.
Modified docker-compose.yaml:

  celery:
    image: openwisp/openwisp-dashboard:latest
    restart: always
    environment:
      - MODULE_NAME=celery
    volumes:
      - openwisp_media:/opt/openwisp/media
      - openwisp_private_storage:/opt/openwisp/private
      - openwisp_ssh:/home/openwisp/.ssh
      - ./customization/configuration/django/:/opt/openwisp/openwisp/configuration:ro
      # overwrite  
      - ./py/ssh.py:/usr/local/lib/python3.12/site-packages/openwisp_controller/connection/connectors/openwrt/ssh.py:ro

[nemesifier]

Glad you solved it! I think you can use the edge images and it should work without the need of that overwrite.