[bug] When logging in with the 2FA account, the corresponding login information is not displayed in the logs.

[OiCkilL]

When logging in with the 2FA account, the corresponding login information is not displayed in the logs.

{
    "baseURL": "https://rewards.bing.com",
    "sessionPath": "sessions",
    "headless": true,
    "parallel": false,
    "runOnZeroPoints": false,
    "clusters": 1,
    "saveFingerprint": {
        "mobile": false,
        "desktop": false
    },
    "workers": {
        "doDailySet": true,
        "doMorePromotions": true,
        "doPunchCards": true,
        "doDesktopSearch": true,
        "doMobileSearch": true,
        "doDailyCheckIn": true,
        "doReadToEarn": true
    },
    "searchOnBingLocalQueries": false,
    "globalTimeout": "30s",
    "searchSettings": {
        "useGeoLocaleQueries": true,
        "scrollRandomResults": true,
        "clickRandomResults": true,
        "searchDelay": {
            "min": "3min",
            "max": "5min"
        },
        "retryMobileSearchAmount": 2
    },
    "logExcludeFunc": [
        "SEARCH-CLOSE-TABS",
        "DISMISS-ALL-MESSAGES"
    ],
    "webhookLogExcludeFunc": [
        "SEARCH-CLOSE-TABS"
    ],
    "proxy": {
        "proxyGoogleTrends": true,
        "proxyBingTerms": true
    },
    "webhook": {
        "enabled": false,
        "url": ""
    }
}

[651Shadow]

Okay I tried something. run it "headless mode false" and in the mobile instance there will be a 2fa prompt, just skip or wtv it says and then stop it when you see the dashboard and run the bot again in "headless mode true" see if it works

[OiCkilL]

Okay I tried something. run it "headless mode false" and in the mobile instance there will be a 2fa prompt, just skip or wtv it says and then stop it when you see the dashboard and run the bot again in "headless mode true" see if it works

not works

[651Shadow]

Go into src then in the config change the "headless to false" and then do npm run build in the main directory And see what does it get stuck on and maybe send a screenshot

[OiCkilL]

[651Shadow]

Haven't seen that one before Can you send a screenshot of the browser?

[OiCkilL]

Haven't seen that one before Can you send a screenshot of the browser?

A docker container, no browser screenshots.

[651Shadow]

Oh you are running it in docker, I see

[basalisco]

when that message appears, during the login procedure even if you have not activated 2FA, for some reason microsoft brings you to a window where it asks you to activate it or if you have entered an email associated with the account it is asking you to enter the verification email to send the 2FA code. I recommend activating the finger print saving option and the first time following the on-screen procedure so that the login procedure is successful

[mgrimace]

when that message appears, during the login procedure even if you have not activated 2FA, for some reason microsoft brings you to a window where it asks you to activate it or if you have entered an email associated with the account it is asking you to enter the verification email to send the 2FA code. I recommend activating the finger print saving option and the first time following the on-screen procedure so that the login procedure is successful

I don't know that that can work for docker and/or headless versions unfortunately. In this case, the best I can think of would be for the user to switch to an MS passwordless solution (if that's an option), which outputs the 2FA into the logs for the user to enter into their authenticator app. Otherwise, the script would have to be updated to automatically enter the user email, then generate a log/notification, then the user would have to go to their email, retrieve the code, then enter the 2FA code into the script (I think). I'm not sure if there's an easier way to solve this

[basalisco]

Run with vscode and Copy folder that the script creates for the account to the path /dist/browser/session/ and Copy to in docker script path.

Il ven 23 mag 2025, 20:43 Michael Cammarata @.***> ha scritto:

mgrimace left a comment (TheNetsky/Microsoft-Rewards-Script#296) https://github.com/TheNetsky/Microsoft-Rewards-Script/issues/296#issuecomment-2905458203

when that message appears, during the login procedure even if you have not activated 2FA, for some reason microsoft brings you to a window where it asks you to activate it or if you have entered an email associated with the account it is asking you to enter the verification email to send the 2FA code. I recommend activating the finger print saving option and the first time following the on-screen procedure so that the login procedure is successful

I don't know that that can work for docker and/or headless versions unfortunately. In this case, the best I can think of would be for the user to switch to an MS passwordless solution (if that's an option), which outputs the 2FA into the logs for the user to enter into their authenticator app. Otherwise, the script would have to be updated to automatically enter the user email, then generate a log/notification, then the user would have to go to their email, retrieve the code, then enter the 2FA code into the script (I think). I'm not sure if there's an easier way to solve this

— Reply to this email directly, view it on GitHub https://github.com/TheNetsky/Microsoft-Rewards-Script/issues/296#issuecomment-2905458203, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3Y3PU64F5VFZ7N75VXRR3275T3JAVCNFSM6AAAAAB5QI6OXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBVGQ2TQMRQGM . You are receiving this because you commented.Message ID: @.***>

[mgrimace]

Run with vscode and Copy folder that the script creates for the account to the path /dist/browser/session/ and Copy to in docker script path.

Thanks, it turned out to actually be an easier fix on my end, I fixed it with #298

[mgrimace]

For 2FA codes not appearing in logs, try rolling back to v1.5.2 of the script

[mgrimace]

In my case, the [MOBILE] issue was appearing in the logs first as a Dismissed: Submit Button repeated entry in 1.52, and the browserfunc.js fix in #286 made the repeated entry stop, but then it became the same issue here of a prompt for a 2FA entry without a code appearing in the logs.

BUT, the 2FA prompt wasn't actually 2FA (in my case). It was actually a screen by MS to save a passkey, which is easily fixed by manually creating a passkey, see #298.

All of that to say, the fix for this might be to roll back the browserfunc.js change from #286 if that's actually preventing real 2FA codes from appearing in the logs, or it might be fixed just by users creating a passkey (see #298 for steps) since for some users like myself the passkey thing was showing up as a 2FA in the logs.

[jordyamc]

I had a similar issue, in my case I have 2FA from the microsoft app, but the script can't extract the number for the 2FA so I had to select a random option until I finally chose the correct one (I know I can disable headless to see the number, but the script have logic to extract the number so this is considered a bug)

[mgrimace]

I had a similar issue, in my case I have 2FA from the microsoft app, but the script can't extract the number for the 2FA so I had to select a random option until I finally chose the correct one (I know I can disable headless to see the number, but the script have logic to extract the number so this is considered a bug)

Interesting, same thing happened to me today for [DESKTOP] login, passwordless login, with no 2FA code printed to logs. I also tried rolling back to 1.52 browserfunct.ts and that didn't do it.

No idea other than to guess randomly which code for the time being.

[mgrimace]

Both docker and the bare-metal script have had updates to login (mobile) and to print 2FA codes to the logs.

• Use the latest updates, delete your existing /sessions folder, and either rebuild the script, or recreate your container.
• You may have to use passwordless on your account.
• The code to enter into MS Authenticator now does display in the logs.
• In docker use docker logs <container_name> or if you happen to use my NTFY branch/PR codes are pushed as notifications by default.