Connection Test From reForis web interface doesn't finish

Software SW bugs discussion
1

I have noticed that after upgrade to Turris 6.0 test connection from web UI doesn’t work anymore.
It shows waiting/working icons on each test type and waits forever.

Running check_connection script from terminal works just fine:

# check_connection 
Pinging 213.81.232.198 ... OK
IPv4 Gateway: OK
Pinging 217.31.205.50 ... OK
Pinging 198.41.0.4 ... OK
Pinging 199.7.83.42 ... OK
Pinging 8.8.8.8 ... OK
IPv4: OK
IPv6 Gateway: UNKNOWN
Pinging 2001:1488:0:3::2 ... FAILED
Pinging 2001:500:3::42 ... FAILED
Pinging 2001:500:2d::d ... FAILED
Pinging 2606:2800:220:6d:26bf:1447:1097:aa7 ... FAILED
IPv6: FAILED
Resolving repo.turris.cz ... OK
Resolving www.nic.cz ... OK
Resolving c.root-servers.net ... OK
DNS: OK
Resolving www.rhybar.cz ... OK
DNSSEC: OK

IPv6 on WAN interface is disabled.
Later update to Turris 6.0.1 didn’t fix the issue.

Is anybody else seeing this problem?
What I can do to test it deeper?

2

Seeing the same here (TO 6.0.1 HBS)… Couldn’t it be related to change from http to https?

3

Had the same problem, as well as failing diagnostics test and no access to the advanced administration module. I removed Sentinel and Pakon, rebooted and now I can get connection test to work, as well as diagnostics.
I have no idea what the root of the problem was, however.

4

I have the same problem, but only in Chrome when connecting to HTTPS.
There is no problem if connecting to HTTP address or in Firefox (even on HTTPS).
it is problably related to FAQ - Turris Documentation.

1 Like
5

Thanks @Skippi , it looks like the issue is caused by this https://crbug.com/1346579 Chromium issue.
I can confirm that Firefox works fine in this case.

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.