Failed to ping without candidate pairs. Connection is not possible yet.

[kovmir]

I run galene behind nginx proxy. I often get a lot of these within a second in galene logs, is that ok?

Dec 12 17:30:04 xxx galene[371]: ice WARNING: 2023/12/12 17:30:04 Failed to ping without candidate pairs. Connection is not possible yet.
Dec 12 17:30:04 xxx galene[371]: ice WARNING: 2023/12/12 17:30:04 Failed to ping without candidate pairs. Connection is not possible yet.
Dec 12 17:30:04 xxx galene[371]: ice WARNING: 2023/12/12 17:30:04 Failed to ping without candidate pairs. Connection is not possible yet.
Dec 12 17:30:04 xxx galene[371]: ice WARNING: 2023/12/12 17:30:04 Failed to ping without candidate pairs. Connection is not possible yet.
Dec 12 17:30:04 xxx galene[371]: ice WARNING: 2023/12/12 17:30:04 Failed to ping without candidate pairs. Connection is not possible yet.
Dec 12 17:30:04 xxx galene[371]: ice INFO: 2023/12/12 17:30:04 Ignoring remote candidate with tcpType active: tcp4 host 192.168.2.22:9
Dec 12 17:30:04 xxx galene[371]: ice INFO: 2023/12/12 17:30:04 Ignoring remote candidate with tcpType active: tcp4 host 192.168.2.22:9
Dec 12 17:30:04 xxx galene[371]: ice INFO: 2023/12/12 17:30:04 Ignoring remote candidate with tcpType active: tcp4 host 192.168.2.22:9
Dec 12 17:30:04 xxx galene[371]: ice INFO: 2023/12/12 17:30:04 Ignoring remote candidate with tcpType active: tcp4 host 192.168.2.22:9

Second question: is it ok to see LAN addresses of clients in logs?

[jech]

I run galene behind nginx proxy. I often get a lot of these within a second in galene logs, is that ok?

Please check the logs for "relay test". Also check on the client (type /relay-test in the chat). If both relay tests are successful, then Galene works fine. (But not necessarily optimally — please read https://galene.org/INSTALL.html#running-behind-a-reverse-proxy.)

Second question: is it ok to see LAN addresses of clients in logs?

Yes, it's fine.