The log file is flooded with daemon.err eco[8311]: call modem.get_sim_signal fail: connect "127.0.0.1 80" fail: Connection refused
*Firmware Type0713release2, v. 4.0
Hi,
The modem.get_sim_signal message shows that eco was unable to connect to the local service on 127.0.0.1:80 .
To help determine whether this is only a local API/Web service issue or is related to the cellular connection, could you please help us check the following when the error occurs?
- Can you still access the GL.iNet Web Admin Panel normally?
- Is the cellular Internet connection still working normally, or does it also disconnect/reconnect at the same time?
- If the error is still occurring, please SSH into the router and share the output of the following commands:
netstat -lntp | grep ':80'
ps | grep -E '[n]ginx|[e]co'
logread | grep -Ei 'nginx|eco|oom|out of memory|killed'
You can refer to the tutorial on logging into the router via SSH:
These results should help us confirm whether the local Web/API service has stopped responding and whether it may be related to the cellular issue.
Thank you for your support and understanding.
The issue is solved: Ngix service must be running.
- the cellular signal LED is turned off without nginx service.
daemon.err eco[8311]: call modem.get_sim_signal fail: connect "127.0.0.1 80" fail: Connection refused- nginx is stopped
Why does the cellular signal LED need webserver?
Hi,
Thank you for the clarification and for confirming the behavior.
The cellular signal LED itself does not require a web server. In the current firmware implementation, eco obtains the modem signal information through a local API on 127.0.0.1:80, which depends on the nginx service.
Therefore, when nginx is stopped, eco cannot retrieve the signal value and the cellular signal LED can no longer be updated correctly.