Does signing in to Yuki fail in your normal browser window, but work in a private or incognito window? Then you can stop looking: there is still data from your previous Yuki login in your browser, and it is getting in the way of the new sign-in method.
You can fix this yourself in a few minutes.
Does this sound familiar?
The symptom differs from browser to browser, but the cause is the same. All of these situations belong here:
- You enter your password, click Sign in, and the same password screen comes back — without any error message.
- You enter your 6-digit code and are then sent back to the previous step, over and over.
- You get an error you can do nothing with, for example a message with a number such as 400 or 404.
- You reach the second step but nothing happens: no notification, no field to type a code into.
- Your password is definitely correct, because entering a wrong one does give you the message that it is incorrect.
So it is not always the same message. What these cases have in common is that you keep going round in circles without doing anything wrong.
The test that confirms it: open a private or incognito window and sign in there. If that works, this is your situation.
Need to get back to work right away? Stay in that private window for now, or use a different browser. You will get in there without any trouble. The steps below then fix it for good.
Why does this happen?
Signing in moves back and forth between the Yuki page and Visma's sign-in system. Along the way, a cookie is stored that remembers your sign-in.
If an old cookie from your previous Yuki login is still there, or your browser blocks that exchange, the cookie never arrives. The sign-in then starts over, or stops at an error. In a private window that old data does not exist, which is why it works there.
In Google Chrome
- Open Yuki in Chrome and click the icon to the left of the address bar.
- Choose Cookies and site data and delete the data for this site.
- Close Chrome completely — every window, not just the tab — and open it again.
If that does not help, allow third-party cookies for the two sites involved. Chrome blocks these ever more strictly, and signing in needs them.
- Type chrome://settings/cookies in your address bar.
- Find the list of sites allowed to use third-party cookies and add: [*.]visma.com and [*.]yuki.be
- Close Chrome completely again and try once more.
More from Google itself: Clear, allow and manage cookies in Chrome.
In Mozilla Firefox
- Open Yuki in Firefox and click the padlock or shield icon to the left of the address bar.
- Choose Clear cookies and site data and confirm.
- Then click the shield icon to the left of the address bar and turn Enhanced Tracking Protection off for this site.
- Close Firefox completely and open it again.
That protection is on by default in Firefox and blocks exchanges between sites — which is exactly what signing in needs. You are only turning it off for Yuki, not for the rest of your browser.
More from Mozilla itself: Clear cookies and site data in Firefox.
In Microsoft Edge
- Open Yuki in Edge and click the padlock icon to the left of the address bar.
- Open Cookies and site permissions and delete the cookies for this site.
- Close Edge completely and open it again.
More from Microsoft itself: Manage cookies in Microsoft Edge.
Still not working?
Two things to check:
- An extension. Privacy and ad blockers can stop the same exchange. Turn your extensions off temporarily and try again.
- A managed workstation. If your IT administrator rolls out browser settings, you may not be able to make these changes yourself. If the problem hits several colleagues at once, that is a strong sign it comes from there. Ask your IT administrator to allow cookies for visma.com and yuki.be.
Still stuck? Email support@yuki.be with these details, so we can look into it straight away:
- your email address and the name of your domain
- which browser you are using
- a screenshot of the error message, if you get one
- whether it does work in a private window