Hi! I understand you're getting an error message when trying to top up on the TfL Go app. Could you please share a bit more detail about the error? For example, what exactly does the message say, and do you see this issue when trying to add credit to any card or a particular card type (like Oyster or Zip Oyster)? Also, have you tried topping up using any other method or the TfL website?
In the meantime, here’s a step-by-step approach we can try to troubleshoot the top-up error on your Linux device using the WebKit browser:
1. Check Internet Connection: Confirm your device has a stable internet connection. 2. Update the App: Since you're on Linux browsing via WebKit, ensure you are accessing the latest version of the TfL Go web app or website. 3. Clear Browser Cache: Sometimes cached data causes issues. Clear the cache and cookies from your browser settings. 4. Try Incognito Mode: Open a private browsing or incognito window in WebKit and try to top up again. This avoids problems with cached data or extensions. 5. Verify Payment Details: Check your payment method details are up to date and valid. 6. Log Out and Log In: If you're logged into an account, try logging out and back in to refresh your session. 7. Try TfL Website: For some card types, especially Zip Oyster cards, top-ups sometimes work better or exclusively via the TfL website rather than the app.
If these don't solve the problem, the error might be related to your specific account or card details, or a temporary issue with TfL systems. In that case, you might want to contact TfL support with the error message details, time/date, and card info here: https://tfl.gov.uk/help-and-contact/contact-us-about-the-tfl-oyster-app
Let me know what the error message says exactly or if you need guidance on any of the above steps! Are you happy to try these suggestions?
Thanks for sharing the exact error message: "Something went wrong. This information is not available now. Please try again in a few minutes." This usually points to a temporary issue with the TfL system or a connection hiccup between your app/browser and TfL servers.
Since you are using the TfL Go app on a Linux device through a WebKit-based browser, here are some tailored next steps to try:
1. Wait and Retry: Sometimes TfL’s backend services experience brief downtime or maintenance. Waiting 10-15 minutes and trying again often resolves it.
2. Clear Your Browser Cache: Your browser cache might have corrupted data causing this. Clear cache and cookies in WebKit and restart the browser.
3. Try a Private/Incognito Window: Open the TfL Go web app in a new private browsing session to avoid cache or cookie conflicts.
4. Disable VPN or Firewall Temporarily: If you have VPN or firewall software running, temporarily disable it as it might block certain connections to TfL servers.
5. Check Network Stability: Ensure your internet connection is stable with no proxy or content filtering interfering.
6. Logout and Login Again: If you’re logged in, sign out and back in to refresh your session tokens.
7. Double Check TfL Service Status: Occasionally, network or server outages affect functionalities. You can check TfL’s service status on their official website or social media for alerts.
Would you like me to guide you through clearing your browser cache or trying incognito mode? Or is there anything else specific you noticed when the error appears?
Comments
Henry Adams
Henry breaks software for a living to ensure quality. He’s a big puzzle fanatic...
Followed by
Hi! I understand you're getting an error message when trying to top up on the TfL Go app. Could you please share a bit more detail about the error? For example, what exactly does the message say, and do you see this issue when trying to add credit to any card or a particular card type (like Oyster or Zip Oyster)? Also, have you tried topping up using any other method or the TfL website?
In the meantime, here’s a step-by-step approach we can try to troubleshoot the top-up error on your Linux device using the WebKit browser:
1. Check Internet Connection: Confirm your device has a stable internet connection.
2. Update the App: Since you're on Linux browsing via WebKit, ensure you are accessing the latest version of the TfL Go web app or website.
3. Clear Browser Cache: Sometimes cached data causes issues. Clear the cache and cookies from your browser settings.
4. Try Incognito Mode: Open a private browsing or incognito window in WebKit and try to top up again. This avoids problems with cached data or extensions.
5. Verify Payment Details: Check your payment method details are up to date and valid.
6. Log Out and Log In: If you're logged into an account, try logging out and back in to refresh your session.
7. Try TfL Website: For some card types, especially Zip Oyster cards, top-ups sometimes work better or exclusively via the TfL website rather than the app.
If these don't solve the problem, the error might be related to your specific account or card details, or a temporary issue with TfL systems. In that case, you might want to contact TfL support with the error message details, time/date, and card info here: https://tfl.gov.uk/help-and-contact/contact-us-about-the-tfl-oyster-app
Let me know what the error message says exactly or if you need guidance on any of the above steps! Are you happy to try these suggestions?
Error message is Something went wrong. This information is not available now. Please try again in a few minutes.
Henry Adams
Henry breaks software for a living to ensure quality. He’s a big puzzle fanatic...
Followed by
Thanks for sharing the exact error message: "Something went wrong. This information is not available now. Please try again in a few minutes." This usually points to a temporary issue with the TfL system or a connection hiccup between your app/browser and TfL servers.
Since you are using the TfL Go app on a Linux device through a WebKit-based browser, here are some tailored next steps to try:
1. Wait and Retry: Sometimes TfL’s backend services experience brief downtime or maintenance. Waiting 10-15 minutes and trying again often resolves it.
2. Clear Your Browser Cache: Your browser cache might have corrupted data causing this. Clear cache and cookies in WebKit and restart the browser.
3. Try a Private/Incognito Window: Open the TfL Go web app in a new private browsing session to avoid cache or cookie conflicts.
4. Disable VPN or Firewall Temporarily: If you have VPN or firewall software running, temporarily disable it as it might block certain connections to TfL servers.
5. Check Network Stability: Ensure your internet connection is stable with no proxy or content filtering interfering.
6. Logout and Login Again: If you’re logged in, sign out and back in to refresh your session tokens.
7. Double Check TfL Service Status: Occasionally, network or server outages affect functionalities. You can check TfL’s service status on their official website or social media for alerts.
If after these steps the issue remains, it might be related to your specific account or card details, in which case contacting TfL support directly would be best. You can reach them here: https://tfl.gov.uk/help-and-contact/contact-us-about-the-tfl-oyster-app 1 3.
Would you like me to guide you through clearing your browser cache or trying incognito mode? Or is there anything else specific you noticed when the error appears?