Need help: My IPv4 rootless podman container (Ubuntu 22.04) comnet has "timed out" issues

All errors are yet again from the non-root nodes.

 INFO 2022-04-17T00:07:45.035001Z [sn/src/node/api/]:
	 ➤ 8f02f4.. Bootstrapping a new node.
 ERROR 2022-04-17T00:08:21.468893Z [/cargo/registry/src/]:
	 ➤ bootstrap
	 ➤ Failed to bootstrap to the network, last error: timed out
 DEBUG 2022-04-17T00:08:21.469938Z [sn/src/node/core/comm/]:
	 ➤ count_msgs
	 ➤ Entered msg counting listener loop.

Command run for node #2 out of 16:

sn_node -vvvv 
--idle-timeout-msec 5500 
--keep-alive-interval-msec 40000 
--public-addr my.ip.v.4 
--log-dir /home/admin/.safe/node_dir_1 
--root-dir /home/admin/.safe/node_dir_1 
--hard-coded-contacts []

ip addr inside container

admin@e7c8edc6d8da:~/.safe/node$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 92:8c:93:6d:59:6c brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet brd scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::908c:93ff:fe6d:596c/64 scope link
       valid_lft forever preferred_lft forever

This topic was automatically closed after 60 days. New replies are no longer allowed.