❌

Normal view

Received — 25 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19048)

✇Twitter @Wegenwerken
By: RSS-Bridge
25 February 2022 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 — 24 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 503! (19047)

✇Twitter @Wegenwerken
By: RSS-Bridge
24 February 2022 at 21: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! (19047)

✇Twitter @Wegenwerken
By: RSS-Bridge
24 February 2022 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 — 23 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19046)

✇Twitter @Wegenwerken
By: RSS-Bridge
23 February 2022 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 — 22 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19045)

✇Twitter @Wegenwerken
By: RSS-Bridge
22 February 2022 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 — 21 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19044)

✇Twitter @Wegenwerken
By: RSS-Bridge
21 February 2022 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 — 20 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19043)

✇Twitter @Wegenwerken
By: RSS-Bridge
20 February 2022 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 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19042)

✇Twitter @Wegenwerken
By: RSS-Bridge
19 February 2022 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 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19041)

✇Twitter @Wegenwerken
By: RSS-Bridge
18 February 2022 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 — 17 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19040)

✇Twitter @Wegenwerken
By: RSS-Bridge
17 February 2022 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 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19039)

✇Twitter @Wegenwerken
By: RSS-Bridge
16 February 2022 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 — 15 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19038)

✇Twitter @Wegenwerken
By: RSS-Bridge
15 February 2022 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 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19037)

✇Twitter @Wegenwerken
By: RSS-Bridge
14 February 2022 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 — 13 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19036)

✇Twitter @Wegenwerken
By: RSS-Bridge
13 February 2022 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 — 12 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19035)

✇Twitter @Wegenwerken
By: RSS-Bridge
12 February 2022 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 — 11 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19034)

✇Twitter @Wegenwerken
By: RSS-Bridge
11 February 2022 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 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19033)

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

Bridge returned error 429! (19032)

✇Twitter @Wegenwerken
By: RSS-Bridge
9 February 2022 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 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19031)

✇Twitter @Wegenwerken
By: RSS-Bridge
8 February 2022 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 — 7 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19030)

✇Twitter @Wegenwerken
By: RSS-Bridge
7 February 2022 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 — 6 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19029)

✇Twitter @Wegenwerken
By: RSS-Bridge
6 February 2022 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 — 5 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19028)

✇Twitter @Wegenwerken
By: RSS-Bridge
5 February 2022 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 — 4 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19027)

✇Twitter @Wegenwerken
By: RSS-Bridge
4 February 2022 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 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19026)

✇Twitter @Wegenwerken
By: RSS-Bridge
3 February 2022 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 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19025)

✇Twitter @Wegenwerken
By: RSS-Bridge
2 February 2022 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 February 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19024)

✇Twitter @Wegenwerken
By: RSS-Bridge
1 February 2022 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 — 31 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19023)

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

Bridge returned error 429! (19022)

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

Bridge returned error 429! (19021)

✇Twitter @Wegenwerken
By: RSS-Bridge
29 January 2022 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 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19020)

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

Bridge returned error 429! (19019)

✇Twitter @Wegenwerken
By: RSS-Bridge
27 January 2022 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 — 26 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19018)

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

Bridge returned error 0! (19017)

✇Twitter @Wegenwerken
By: RSS-Bridge
25 January 2022 at 20:32

Twitter @Wegenwerken was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to api.twitter.com:443 (35)
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! (19017)

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

Bridge returned error 429! (19016)

✇Twitter @Wegenwerken
By: RSS-Bridge
24 January 2022 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 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 429! (19015)

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

Bridge returned error 429! (19014)

✇Twitter @Wegenwerken
By: RSS-Bridge
22 January 2022 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

Bridge returned error 429! (19013)

✇Twitter @Wegenwerken
By: RSS-Bridge
22 January 2022 at 01: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 — 21 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (19013)

✇Twitter @Wegenwerken
By: RSS-Bridge
21 January 2022 at 02: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

Received — 20 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (19012)

✇Twitter @Wegenwerken
By: RSS-Bridge
20 January 2022 at 02: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 — 19 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (19011)

✇Twitter @Wegenwerken
By: RSS-Bridge
19 January 2022 at 02:16

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 — 18 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (19010)

✇Twitter @Wegenwerken
By: RSS-Bridge
18 January 2022 at 02:16

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 — 17 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (19009)

✇Twitter @Wegenwerken
By: RSS-Bridge
17 January 2022 at 02: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

❌