Hi again.
Okey. Thanks to a last month update of the hardware i’m using got a socks5 proxy working.
root@23d02a5:~# curl -sSf -x socks4://192.168.15.30:1080 http://185.99.****/
curl: (7) Failed to receive SOCKS4 connect request ack.
root@23d02a5:~# curl -sSf -x socks5://192.168.15.30:1080 http://185.99.****/
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
body {
width: 35em;
margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif;
}
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
</html>
Still no connection.
Tried the 0.0.0.0 and 127.0.0.1 local ip in config. No luck.
getaddrinfo errors are still there
root@23d02a5:~# journalctl -u resin-sup* --all
-- Logs begin at Sat 2013-01-19 00:29:24 UTC, end at Thu 2020-12-03 16:53:05 UTC. --
Dec 03 16:48:48 23d02a5 systemd[1]: Starting Resin supervisor...
Dec 03 16:48:49 23d02a5 resin-supervisor[1198]: resin_supervisor
Dec 03 16:48:49 23d02a5 resin-supervisor[1224]: active
Dec 03 16:48:49 23d02a5 systemd[1]: Started Resin supervisor.
Dec 03 16:48:49 23d02a5 resin-supervisor[1227]: Container config has not changed
Dec 03 16:48:55 23d02a5 resin-supervisor[1227]: Starting system message bus: dbus.
Dec 03 16:48:55 23d02a5 resin-supervisor[1227]: * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
Dec 03 16:48:56 23d02a5 resin-supervisor[1227]: ...done.
Dec 03 16:49:02 23d02a5 resin-supervisor[1227]: (node:1) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods >
Dec 03 16:49:02 23d02a5 resin-supervisor[1227]: Starting event tracker
Dec 03 16:49:02 23d02a5 resin-supervisor[1227]: Starting up api binder
Dec 03 16:49:02 23d02a5 resin-supervisor[1227]: Starting logging infrastructure
Dec 03 16:49:02 23d02a5 resin-supervisor[1227]: Event: Supervisor start {}
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Performing database cleanup for container log timestamps
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Connectivity check enabled: true
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Starting periodic check for IP addresses
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Reporting initial state, supervisor version and API info
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Waiting for connectivity...
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Skipping preloading
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Starting API server
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Applying target state
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Ensuring device is provisioned
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Starting current state report
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Starting target state poll
Dec 03 16:49:03 23d02a5 resin-supervisor[1227]: Supervisor API listening on all interfaces
Dec 03 16:49:04 23d02a5 resin-supervisor[1227]: Finished applying target state
Dec 03 16:49:04 23d02a5 resin-supervisor[1227]: Apply success!
Dec 03 16:49:13 23d02a5 resin-supervisor[1227]: Failed to get target state for device: Error: getaddrinfo EAI_AGAIN api.balena-cloud.com api.balena-cloud.com:443
Dec 03 16:49:38 23d02a5 resin-supervisor[1227]: Failed to get target state for device: Error: getaddrinfo EAI_AGAIN api.balena-cloud.com api.balena-cloud.com:443
Dec 03 16:50:18 23d02a5 resin-supervisor[1227]: Failed to get target state for device: Error: getaddrinfo EAI_AGAIN api.balena-cloud.com api.balena-cloud.com:443
Dec 03 16:51:28 23d02a5 resin-supervisor[1227]: Failed to get target state for device: Error: getaddrinfo EAI_AGAIN api.balena-cloud.com api.balena-cloud.com:443
Updating previous info, everything seems the same.
root@23d02a5:~# journalctl -u resin-proxy-config
-- Logs begin at Sat 2013-01-19 00:21:23 UTC, end at Thu 2020-12-03 16:54:00 UTC. --
Dec 03 16:48:25 23d02a5 systemd[1]: Starting Resin proxy configuration service...
Dec 03 16:48:25 23d02a5 sh[740]: resin-proxy-config: Found config.json in /mnt/boot/config.json .
Dec 03 16:48:25 23d02a5 sh[740]: iptables: No chain/target/match by that name.
Dec 03 16:48:25 23d02a5 sh[740]: iptables: No chain/target/match by that name.
Dec 03 16:48:25 23d02a5 sh[740]: iptables v1.6.2: Couldn't load target `REDSOCKS':No such file or directory
Dec 03 16:48:25 23d02a5 sh[740]: Try `iptables -h' or 'iptables --help' for more information.
Dec 03 16:48:25 23d02a5 sh[740]: iptables v1.6.2: Couldn't load target `REDSOCKS':No such file or directory
Dec 03 16:48:25 23d02a5 sh[740]: Try `iptables -h' or 'iptables --help' for more information.
Dec 03 16:48:25 23d02a5 sh[740]: iptables v1.6.2: Couldn't load target `REDSOCKS':No such file or directory
Dec 03 16:48:25 23d02a5 sh[740]: Try `iptables -h' or 'iptables --help' for more information.
Dec 03 16:48:25 23d02a5 sh[740]: iptables: No chain/target/match by that name.
Dec 03 16:48:25 23d02a5 sh[740]: iptables: No chain/target/match by that name.
Dec 03 16:48:25 23d02a5 systemd[1]: Started Resin proxy configuration service.
root@23d02a5:~# systemctl status redsocks.service
● redsocks.service - redsocks transparent proxy redirector
Loaded: loaded (/lib/systemd/system/redsocks.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2020-12-03 16:48:25 UTC; 3min 23s ago
Main PID: 800 (redsocks)
CGroup: /system.slice/redsocks.service
└─800 /usr/bin/redsocks -c /mnt/boot/system-proxy/redsocks.conf
Dec 03 16:48:25 23d02a5 systemd[1]: Started redsocks transparent proxy redirector.
Dec 03 16:48:25 23d02a5 redsocks[800]: 1607014105.660122 warning redsocks.c:177 redsocks_onexit(...) Overwriting `redsocks:local_ip` entry: it needs to match OS' iptables configuration.
root@23d02a5:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy DROP)
target prot opt source destination
DOCKER-USER all -- anywhere anywhere
DOCKER-ISOLATION-STAGE-1 all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain DOCKER (3 references)
target prot opt source destination
Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target prot opt source destination
DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere
DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere
DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere
RETURN all -- anywhere anywhere
Chain DOCKER-ISOLATION-STAGE-2 (3 references)
target prot opt source destination
DROP all -- anywhere anywhere
DROP all -- anywhere anywhere
DROP all -- anywhere anywhere
RETURN all -- anywhere anywhere
Chain DOCKER-USER (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
Im still suspicios of that message
Overwriting
redsocks:local_ipentry: it needs to match OS’ iptables configuration
And the
iptables v1.6.2: Couldn’t load target `REDSOCKS’:No such file or directory