Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

crash on new bahn.de login page

more options

i try to login on bahn.de. they redesigned the login-procedure recently. and with the new login it crashes the Firefox tab reproducible on my phone. i get the `Firefox can't load that page` message. on of the crash reports can be found at https://crash-stats.mozilla.org/report/index/d3962d01-f863-4f6c-908d-3d4af0211103

i have cleaned up with `Privacy and Security` - `Delete browsing data` (all options set) and also did clean the cash for the firefox app from the system settings.

the url is (i removed the nonce and state values) https://accounts.bahn.de/auth/realms/db/protocol/openid-connect/auth?cancel_uri=https%3A%2F%2Ffahrkarten.bahn.de%2Fprivatkunde%2Flogin%2Fidmredirect.post%3Flang%3Dde%26country%3DDEU%26scope%3DCANCEL&showRegisterWithBahnCard=true&kc_locale=de&showSoftLogin=true&scope=openid&response_type=code&redirect_uri=https%3A%2F%2Ffahrkarten.bahn.de%2Fprivatkunde%2Flogin%2Fidmredirect.post%3Flang%3Dde%26country%3DDEU%26scope%3DRETURN&state=0&showReloginMessage=false&nonce=0&client_id=fe_esuite

the original url was 551 characters long.

my first impression was that the url may be to long.. i tried to shorten it - https://accounts.bahn.de/auth/realms/db/protocol/openid-connect/auth?cancel_uri=https%3A%2F%2Fbahn.de&kc_locale=de&showSoftLogin=true&scope=openid&response_type=code&redirect_uri=https%3A%2F%2Ffahrkarten.bahn.de&state=0&nonce=0&client_id=fe_esuite (247 characters) this one worked in the desktop browser but also crashes in firefox android. the crash happens latest when i click on the `Angemeldet bleiben` checkbox. on a next try it happened shortly after the loading without user interaction.

Firefox Version: ``` 93.2.0 (Build #2015839745) AC: 93.0.12, e39f5dba3f GV: 93.0-20210927210923 AS: 82.1.0 ```

OS ``` Android 7.1.2 LineageOS 14.1 ``` and yes - i know this is a very outdated OS version...


the main problem is that this login is needed to authenticate in the *db navigator app*.

with some workarounds i managed to do a successful login in the app:

  • switch system default browser to the *stock browser* app
  • click login button in *db navigator app*
  • stock browser opens with login page
  • fill in & click login
  • stock browser does not know how to handle returned url (example below)
  • copy returned url to clipboard
  • open firefox
  • past url
  • open menu and click on *open in app*
  • *db navigator app* launches and accepts the login
  • i am happy again ;-)



hopefully this is only the case for such old OS versions and this way does not effect anyone else...


are there any other things i can do for better fix the issue in the first place?

i try to login on bahn.de. they redesigned the login-procedure recently. and with the new login it crashes the Firefox tab reproducible on my phone. i get the `Firefox can't load that page` message. on of the crash reports can be found at https://crash-stats.mozilla.org/report/index/d3962d01-f863-4f6c-908d-3d4af0211103 i have cleaned up with `Privacy and Security` - `Delete browsing data` (all options set) and also did clean the cash for the firefox app from the system settings. the url is (i removed the nonce and state values) https://accounts.bahn.de/auth/realms/db/protocol/openid-connect/auth?cancel_uri=https%3A%2F%2Ffahrkarten.bahn.de%2Fprivatkunde%2Flogin%2Fidmredirect.post%3Flang%3Dde%26country%3DDEU%26scope%3DCANCEL&showRegisterWithBahnCard=true&kc_locale=de&showSoftLogin=true&scope=openid&response_type=code&redirect_uri=https%3A%2F%2Ffahrkarten.bahn.de%2Fprivatkunde%2Flogin%2Fidmredirect.post%3Flang%3Dde%26country%3DDEU%26scope%3DRETURN&state=0&showReloginMessage=false&nonce=0&client_id=fe_esuite the original url was 551 characters long. my first impression was that the url may be to long.. i tried to shorten it - https://accounts.bahn.de/auth/realms/db/protocol/openid-connect/auth?cancel_uri=https%3A%2F%2Fbahn.de&kc_locale=de&showSoftLogin=true&scope=openid&response_type=code&redirect_uri=https%3A%2F%2Ffahrkarten.bahn.de&state=0&nonce=0&client_id=fe_esuite (247 characters) this one worked in the desktop browser but also crashes in firefox android. the crash happens latest when i click on the `Angemeldet bleiben` checkbox. on a next try it happened shortly after the loading without user interaction. Firefox Version: ``` 93.2.0 (Build #2015839745) AC: 93.0.12, e39f5dba3f GV: 93.0-20210927210923 AS: 82.1.0 ``` OS ``` Android 7.1.2 LineageOS 14.1 ``` and yes - i know this is a very outdated OS version... the main problem is that this login is needed to authenticate in the *db navigator app*. with some workarounds i managed to do a successful login in the app: * switch system default browser to the *stock browser* app * click login button in *db navigator app* * stock browser opens with login page * fill in & click login * stock browser does not know how to handle returned url (example below) * copy returned url to clipboard * open firefox * past url * open menu and click on *open in app* * *db navigator app* launches and accepts the login * i am happy again ;-) hopefully this is only the case for such old OS versions and this way does not effect anyone else... are there any other things i can do for better fix the issue in the first place?
Attached screenshots

Chosen solution

Hi Stefan

Thank you for your question.

What level of enhanced trackin protection do you have set?

Do you have any add-ons installed?

Firefox for Android 94 is currently being rolled out. Please can you check with this version when you get the update?

Read this answer in context 👍 0

All Replies (2)

more options

Chosen Solution

Hi Stefan

Thank you for your question.

What level of enhanced trackin protection do you have set?

Do you have any add-ons installed?

Firefox for Android 94 is currently being rolled out. Please can you check with this version when you get the update?

more options

Hi Seburo,

the update arrived not as quick on my phone as needed to test... - as i have now switched to a new phone ;-)

so i think we can see this as solved.. (outdated at least!)