❌

Normal view

Received — 3 February 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19026)

3 February 2022 at 02:02

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 2 February 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19025)

2 February 2022 at 02:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 1 February 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19024)

1 February 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 31 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19023)

31 January 2022 at 02:17

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 30 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19022)

30 January 2022 at 02:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 29 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19021)

29 January 2022 at 02:02

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 28 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19020)

28 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 27 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19019)

27 January 2022 at 02:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 26 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19018)

26 January 2022 at 02:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 25 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19017)

25 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 24 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19016)

24 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 23 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19015)

23 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 22 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 429! (19014)

22 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Bridge returned error 429! (19013)

22 January 2022 at 01:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 21 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19013)

21 January 2022 at 02:17

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 20 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19012)

20 January 2022 at 02:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 19 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19011)

19 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 18 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19010)

18 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 17 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19009)

17 January 2022 at 02:02

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 16 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19008)

16 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 15 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19007)

15 January 2022 at 02:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 14 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19006)

14 January 2022 at 02:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 13 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19005)

13 January 2022 at 02:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 12 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19004)

12 January 2022 at 02:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 11 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19003)

11 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 10 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19002)

10 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 9 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19001)

9 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 8 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (19000)

8 January 2022 at 02:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 7 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18999)

7 January 2022 at 02:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 6 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18998)

6 January 2022 at 03:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 5 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18997)

5 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 4 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18996)

4 January 2022 at 02:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 3 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18995)

3 January 2022 at 19:31

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 2 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18994)

2 January 2022 at 16:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 1 January 2022 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18993)

1 January 2022 at 17:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 31 December 2021 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18992)

31 December 2021 at 03:17

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 30 December 2021 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18991)

30 December 2021 at 10:16

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 25 December 2021 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18986)

25 December 2021 at 19:01

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 24 December 2021 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18985)

24 December 2021 at 07:31

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 16 December 2021 ⏭ Twitter @HELI_FEDPOLFED

Bridge returned error 500! (18977)

16 December 2021 at 18:46

Twitter @HELI_FEDPOLFED was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=HELI_FEDPOLFED&bridge=Twitter&format=Atom`
Version: `dev.2021-04-25`

  • Press Return to check your input parameters
  • Press F5 to retry
  • Check if this issue was already reported on GitHub (give it a thumbs-up)
  • Open a GitHub Issue if this error persists

pmaziere

Received — 13 November 2021 ⏭ Twitter @HELI_FEDPOLFED
Received — 10 November 2021 ⏭ Twitter @HELI_FEDPOLFED
❌