❌

Normal view

Received — 15 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19038)

15 February 2022 at 02:16

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19037)

14 February 2022 at 02:02

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19036)

13 February 2022 at 02:17

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19035)

12 February 2022 at 02:16

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19034)

11 February 2022 at 02:01

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19033)

10 February 2022 at 02:16

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19032)

9 February 2022 at 02:02

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19031)

8 February 2022 at 02:01

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19030)

7 February 2022 at 02:01

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19029)

6 February 2022 at 02:02

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19028)

5 February 2022 at 02:01

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19027)

4 February 2022 at 02:02

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 February 2022 ⏭ Twitter @FlitscontroleBE

Bridge returned error 429! (19026)

3 February 2022 at 02:01

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19025)

2 February 2022 at 02:01

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19024)

1 February 2022 at 02:16

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19023)

31 January 2022 at 02:16

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19022)

30 January 2022 at 02:01

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19021)

29 January 2022 at 02:01

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19020)

28 January 2022 at 02:16

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19019)

27 January 2022 at 02:01

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19018)

26 January 2022 at 02:16

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19017)

25 January 2022 at 02:01

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19016)

24 January 2022 at 02:16

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19015)

23 January 2022 at 02:16

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19014)

22 January 2022 at 02:17

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 @FlitscontroleBE

Bridge returned error 429! (19013)

21 January 2022 at 18:17

Twitter @FlitscontroleBE 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=FlitscontroleBE&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 500! (19013)

21 January 2022 at 02:17

Twitter @FlitscontroleBE was unable to receive or process the remote website's content!
Error message: `Could not parse guest token`
Query string: `action=display&u=FlitscontroleBE&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 @FlitscontroleBE
❌