❌

Normal view

Received — 18 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19434)

✇Twitter @Wegenwerken
By: RSS-Bridge
18 March 2023 at 02:01

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19433)

✇Twitter @Wegenwerken
By: RSS-Bridge
17 March 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19432)

✇Twitter @Wegenwerken
By: RSS-Bridge
16 March 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19431)

✇Twitter @Wegenwerken
By: RSS-Bridge
15 March 2023 at 02:17

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19430)

✇Twitter @Wegenwerken
By: RSS-Bridge
14 March 2023 at 02:17

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19429)

✇Twitter @Wegenwerken
By: RSS-Bridge
13 March 2023 at 02:01

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (19428)

✇Twitter @Wegenwerken
By: RSS-Bridge
12 March 2023 at 11:02

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

✇Twitter @Wegenwerken
By: RSS-Bridge
12 March 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19427)

✇Twitter @Wegenwerken
By: RSS-Bridge
11 March 2023 at 02:01

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19426)

✇Twitter @Wegenwerken
By: RSS-Bridge
10 March 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19425)

✇Twitter @Wegenwerken
By: RSS-Bridge
9 March 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (19424)

✇Twitter @Wegenwerken
By: RSS-Bridge
8 March 2023 at 07:46

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

✇Twitter @Wegenwerken
By: RSS-Bridge
8 March 2023 at 02:16

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 503! (19423)

✇Twitter @Wegenwerken
By: RSS-Bridge
7 March 2023 at 23:02

Twitter @Wegenwerken 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=Wegenwerken&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! (19423)

✇Twitter @Wegenwerken
By: RSS-Bridge
7 March 2023 at 02:01

Twitter @Wegenwerken 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=Wegenwerken&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! (19422)

✇Twitter @Wegenwerken
By: RSS-Bridge
7 March 2023 at 01:01

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

Bridge returned error 403! (19422)

✇Twitter @Wegenwerken
By: RSS-Bridge
6 March 2023 at 19:16

Twitter @Wegenwerken 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=Wegenwerken&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! (19422)

✇Twitter @Wegenwerken
By: RSS-Bridge
6 March 2023 at 02:16

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19421)

✇Twitter @Wegenwerken
By: RSS-Bridge
5 March 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19420)

✇Twitter @Wegenwerken
By: RSS-Bridge
4 March 2023 at 02:01

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19419)

✇Twitter @Wegenwerken
By: RSS-Bridge
3 March 2023 at 02:01

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19418)

✇Twitter @Wegenwerken
By: RSS-Bridge
2 March 2023 at 02:01

Twitter @Wegenwerken 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=Wegenwerken&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 March 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19417)

✇Twitter @Wegenwerken
By: RSS-Bridge
1 March 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19416)

✇Twitter @Wegenwerken
By: RSS-Bridge
28 February 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19415)

✇Twitter @Wegenwerken
By: RSS-Bridge
27 February 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 503! (19414)

✇Twitter @Wegenwerken
By: RSS-Bridge
26 February 2023 at 23:32

Twitter @Wegenwerken 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=Wegenwerken&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 302! (19414)

✇Twitter @Wegenwerken
By: RSS-Bridge
26 February 2023 at 15:16

Twitter @Wegenwerken was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: Maximum (20) redirects followed (47)
PHP error: `
Query string: `action=display&u=Wegenwerken&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! (19414)

✇Twitter @Wegenwerken
By: RSS-Bridge
26 February 2023 at 02:16

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19413)

✇Twitter @Wegenwerken
By: RSS-Bridge
25 February 2023 at 02:16

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (19412)

✇Twitter @Wegenwerken
By: RSS-Bridge
24 February 2023 at 15:17

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

✇Twitter @Wegenwerken
By: RSS-Bridge
24 February 2023 at 02:16

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19411)

✇Twitter @Wegenwerken
By: RSS-Bridge
23 February 2023 at 02:17

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19410)

✇Twitter @Wegenwerken
By: RSS-Bridge
22 February 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19409)

✇Twitter @Wegenwerken
By: RSS-Bridge
21 February 2023 at 02:01

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19408)

✇Twitter @Wegenwerken
By: RSS-Bridge
20 February 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19407)

✇Twitter @Wegenwerken
By: RSS-Bridge
19 February 2023 at 02:16

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19406)

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

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19405)

✇Twitter @Wegenwerken
By: RSS-Bridge
17 February 2023 at 02:16

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19404)

✇Twitter @Wegenwerken
By: RSS-Bridge
16 February 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 February 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19403)

✇Twitter @Wegenwerken
By: RSS-Bridge
15 February 2023 at 02:16

Twitter @Wegenwerken 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=Wegenwerken&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 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19402)

✇Twitter @Wegenwerken
By: RSS-Bridge
14 February 2023 at 02:16

Twitter @Wegenwerken 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=Wegenwerken&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 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19401)

✇Twitter @Wegenwerken
By: RSS-Bridge
13 February 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19400)

✇Twitter @Wegenwerken
By: RSS-Bridge
12 February 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19399)

✇Twitter @Wegenwerken
By: RSS-Bridge
11 February 2023 at 02:02

Twitter @Wegenwerken 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=Wegenwerken&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 2023 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19398)

✇Twitter @Wegenwerken
By: RSS-Bridge
10 February 2023 at 02:01

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

Bridge returned error 429! (19397)

✇Twitter @Wegenwerken
By: RSS-Bridge
9 February 2023 at 02:17

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

Bridge returned error 429! (19396)

✇Twitter @Wegenwerken
By: RSS-Bridge
8 February 2023 at 13:02

Twitter @Wegenwerken 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=Wegenwerken&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 @Wegenwerken
By: RSS-Bridge
8 February 2023 at 02:16

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

Bridge returned error 401! (19395)

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

Twitter @Wegenwerken 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=Wegenwerken&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 @Wegenwerken
By: RSS-Bridge
7 February 2023 at 02:17

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

❌