❌

Normal view

Received — 10 February 2023 ⏭ Flitsers

Bridge returned error 429! (19398)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
10 February 2023 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 — 9 February 2023 ⏭ Flitsers

Bridge returned error 429! (19397)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
9 February 2023 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 — 8 February 2023 ⏭ Flitsers

Bridge returned error 429! (19396)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
8 February 2023 at 13: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

Bridge returned error 401! (19396)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
8 February 2023 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 — 7 February 2023 ⏭ Flitsers

Bridge returned error 401! (19395)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
7 February 2023 at 14:32

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 429! (19395)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
7 February 2023 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 — 6 February 2023 ⏭ Flitsers

Bridge returned error 429! (19394)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
6 February 2023 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 2023 ⏭ Flitsers

Bridge returned error 429! (19393)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
5 February 2023 at 02:18

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 2023 ⏭ Flitsers

Bridge returned error 429! (19392)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
4 February 2023 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 — 3 February 2023 ⏭ Flitsers

Bridge returned error 503! (19391)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
3 February 2023 at 18: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

Bridge returned error 429! (19391)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
3 February 2023 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 2023 ⏭ Flitsers

Bridge returned error 429! (19390)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
2 February 2023 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 — 1 February 2023 ⏭ Flitsers

Bridge returned error 429! (19389)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
1 February 2023 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 2023 ⏭ Flitsers

Bridge returned error 429! (19388)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
31 January 2023 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 2023 ⏭ Flitsers

Bridge returned error 429! (19387)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
30 January 2023 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 2023 ⏭ Flitsers

Bridge returned error 429! (19386)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
29 January 2023 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 — 28 January 2023 ⏭ Flitsers

Bridge returned error 429! (19385)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
28 January 2023 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 — 27 January 2023 ⏭ Flitsers

Bridge returned error 429! (19384)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
27 January 2023 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 2023 ⏭ Flitsers

Bridge returned error 429! (19383)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
26 January 2023 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 — 25 January 2023 ⏭ Flitsers

Bridge returned error 429! (19382)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
25 January 2023 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 — 24 January 2023 ⏭ Flitsers

Bridge returned error 429! (19381)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
24 January 2023 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 2023 ⏭ Flitsers

Bridge returned error 429! (19380)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
23 January 2023 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 — 22 January 2023 ⏭ Flitsers

Bridge returned error 500! (19379)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
22 January 2023 at 11: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

Bridge returned error 429! (19379)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
22 January 2023 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 — 21 January 2023 ⏭ Flitsers

Bridge returned error 429! (19378)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
21 January 2023 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 — 20 January 2023 ⏭ Flitsers

Bridge returned error 429! (19377)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
20 January 2023 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 — 19 January 2023 ⏭ Flitsers

Bridge returned error 429! (19376)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
19 January 2023 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 — 18 January 2023 ⏭ Flitsers

Bridge returned error 429! (19375)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
18 January 2023 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 — 17 January 2023 ⏭ Flitsers

Bridge returned error 429! (19374)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
17 January 2023 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 — 16 January 2023 ⏭ Flitsers

Bridge returned error 429! (19373)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
16 January 2023 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 — 15 January 2023 ⏭ Flitsers

Bridge returned error 429! (19372)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
15 January 2023 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 January 2023 ⏭ Flitsers

Bridge returned error 429! (19371)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
14 January 2023 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 January 2023 ⏭ Flitsers

Bridge returned error 429! (19370)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
13 January 2023 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 January 2023 ⏭ Flitsers

Bridge returned error 429! (19369)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
12 January 2023 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 — 11 January 2023 ⏭ Flitsers

Bridge returned error 429! (19368)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
11 January 2023 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 — 10 January 2023 ⏭ Flitsers

Bridge returned error 429! (19367)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
10 January 2023 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 — 9 January 2023 ⏭ Flitsers

Bridge returned error 429! (19366)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
9 January 2023 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 — 8 January 2023 ⏭ Flitsers

Bridge returned error 429! (19365)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
8 January 2023 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 — 7 January 2023 ⏭ Flitsers

Bridge returned error 429! (19364)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
7 January 2023 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 — 6 January 2023 ⏭ Flitsers

Bridge returned error 429! (19363)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
6 January 2023 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 — 5 January 2023 ⏭ Flitsers

Bridge returned error 429! (19362)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
5 January 2023 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 — 4 January 2023 ⏭ Flitsers

Bridge returned error 429! (19361)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
4 January 2023 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 January 2023 ⏭ Flitsers

Bridge returned error 429! (19360)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
3 January 2023 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 January 2023 ⏭ Flitsers

Bridge returned error 429! (19359)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
2 January 2023 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 January 2023 ⏭ Flitsers

Bridge returned error 503! (19358)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
1 January 2023 at 20: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 429! (19358)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
1 January 2023 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 — 31 December 2022 ⏭ Flitsers

Bridge returned error 429! (19357)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
31 December 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 — 30 December 2022 ⏭ Flitsers

Bridge returned error 429! (19356)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
30 December 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 — 29 December 2022 ⏭ Flitsers

Bridge returned error 429! (19355)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
29 December 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 — 28 December 2022 ⏭ Flitsers

Bridge returned error 429! (19354)

✇Twitter @FlitscontroleBE
By: RSS-Bridge
28 December 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

❌