June 2020 - anti-censorship-alerts - lists.torproject.org

monit alert -- Connection failed bridgedb-web
by Monit 24 Jun '20

24 Jun '20

Connection failed Service bridgedb-web Date: Wed, 24 Jun 2020 22:42:13 Action: alert Host: server01 Description: failed protocol test [HTTP] at [bridges.torproject.org]:443/ [TCP/IP TLS] -- Connection timed out

1 0

monit alert -- Connection failed wolpertinger-web
by Monit 24 Jun '20

24 Jun '20

Connection failed Service wolpertinger-web Date: Wed, 24 Jun 2020 22:42:03 Action: alert Host: server01 Description: failed protocol test [HTTP] at [bridges.torproject.org]:443/wolpertinger/ [TCP/IP TLS] -- Connection timed out

1 0

monit alert -- Connection succeeded bridgedb-web
by Monit 23 Jun '20

23 Jun '20

Connection succeeded Service bridgedb-web Date: Tue, 23 Jun 2020 04:01:00 Action: alert Host: server01 Description: connection succeeded to [bridges.torproject.org]:443/ [TCP/IP TLS]

1 0

monit alert -- Connection failed bridgedb-web
by Monit 23 Jun '20

23 Jun '20

Connection failed Service bridgedb-web Date: Tue, 23 Jun 2020 03:50:54 Action: alert Host: server01 Description: failed protocol test [HTTP] at [bridges.torproject.org]:443/ [TCP/IP TLS] -- HTTP error: Server returned status 503

1 0

monit alert -- Connection succeeded wolpertinger-web
by Monit 17 Jun '20

17 Jun '20

Connection succeeded Service wolpertinger-web Date: Wed, 17 Jun 2020 19:50:09 Action: alert Host: server01 Description: connection succeeded to [bridges.torproject.org]:443/wolpertinger/ [TCP/IP TLS]

2 1

monit alert -- Connection failed wolpertinger-web
by Monit 17 Jun '20

17 Jun '20

Connection failed Service wolpertinger-web Date: Wed, 17 Jun 2020 15:59:10 Action: alert Host: server01 Description: failed protocol test [HTTP] at [bridges.torproject.org]:443/wolpertinger/ [TCP/IP TLS] -- HTTP error: Server returned status 404

1 0

FYI: Changed default bridge alerts to 3/5 failed tests
by Philipp Winter 15 Jun '20

15 Jun '20

To reduce the number of alerts caused by transient issues, I changed our monit config so we only get alerted if a default bridge fails three out of five consecutive checks.

1 0

monit alert -- Connection succeeded default-bridge-toke-2
by Monit 13 Jun '20

13 Jun '20

Connection succeeded Service default-bridge-toke-2 Date: Sat, 13 Jun 2020 15:26:37 Action: alert Host: server01 Description: connection succeeded to [2a0c:4d80:42:702::1]:27015 [TCP/IP]

1 0

monit alert -- Connection succeeded default-bridge-toke-1
by Monit 13 Jun '20

13 Jun '20

Connection succeeded Service default-bridge-toke-1 Date: Sat, 13 Jun 2020 15:26:36 Action: alert Host: server01 Description: connection succeeded to [45.145.95.6]:27015 [TCP/IP]

1 0

monit alert -- Connection failed default-bridge-toke-2
by Monit 13 Jun '20

13 Jun '20

Connection failed Service default-bridge-toke-2 Date: Sat, 13 Jun 2020 15:16:33 Action: alert Host: server01 Description: failed protocol test [DEFAULT] at [2a0c:4d80:42:702::1]:27015 [TCP/IP] -- Connection timed out

1 0

2024

2023

2022

2021

2020

anti-censorship-alerts June 2020