❌

Normal view

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

Received — 16 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (19008)

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

Bridge returned error 500! (19007)

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

Bridge returned error 500! (19006)

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

Bridge returned error 500! (19005)

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

Received — 12 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (19004)

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

Bridge returned error 500! (19003)

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

Bridge returned error 500! (19002)

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

Bridge returned error 500! (19001)

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

Bridge returned error 500! (19000)

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

Received — 7 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (18999)

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

Bridge returned error 500! (18998)

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

Bridge returned error 500! (18997)

✇Twitter @Wegenwerken
By: RSS-Bridge
5 January 2022 at 04: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 — 3 January 2022 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (18995)

✇Twitter @Wegenwerken
By: RSS-Bridge
3 January 2022 at 20:31

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

Bridge returned error 500! (18994)

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

Bridge returned error 500! (18993)

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

Received — 31 December 2021 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (18992)

✇Twitter @Wegenwerken
By: RSS-Bridge
31 December 2021 at 03: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 — 30 December 2021 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (18991)

✇Twitter @Wegenwerken
By: RSS-Bridge
30 December 2021 at 08:31

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 — 28 December 2021 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (18989)

✇Twitter @Wegenwerken
By: RSS-Bridge
28 December 2021 at 10: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

Received — 26 December 2021 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (18987)

✇Twitter @Wegenwerken
By: RSS-Bridge
26 December 2021 at 04: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

Received — 25 December 2021 ⏭ Twitter @Wegenwerken

Bridge returned error 500! (18986)

✇Twitter @Wegenwerken
By: RSS-Bridge
25 December 2021 at 02: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

❌