https://bugs.kde.org/show_bug.cgi?id=513244
--- Comment #11 from Max Brosnahan <[email protected]> --- I am seeing this issue as well. I debugged it with: `flatpak run --env=KPUBLICTRANSPORT_LOG_DIR=/tmp/kpt-logs org.kde.itinerary` followed by: `flatpak run --command=sh org.kde.itinerary -c 'cat /tmp/kpt-logs/de_db/*'` I attached the logs from the above. The response is a 403 with the response body of: {"status":"ERROR","code":"OPS_BLOCKED","errorRefId": "0.64e11602.1789667542.1365f3c8"}. Should this be shown as an error rather than "No journeys found"? I also wondered about falling back to another provider. I tested this by disabling the bahn.de source and was able to find the train I was looking for. -- You are receiving this mail because: You are watching all bug changes.
