RE: V4V.app will be down Wednesday 11th February 10am UTC - NOW WORKING
(Edited)
You are viewing a single comment's thread:
V4V app is still not working with keychain.
No keychain signature window appears to sign into the app, just this message at the bottom of the screen...
AxiosError: Request failed with status code 401
I'm guessing this is still a server side issue?
EDIT: Still the same issue as above 20/02/2026 @brianoflondon @v4vapp
Any further news on when V4VAPP will be functioning?
Cheers
0
0
0.000
Please try to clear the browser cookies and history for the site, download a fresh version. I think you might still have an old version of the site.
Open the menu on the right with the three lines and look down the bottom, you need to see version 2.2.4.
Thanks for your swift response
@brianoflondon
I cleared all browser data on chrome, history, cookies etc and I have the same problem with version 2.2.4 as can be seen in this screenshot. I have even tried logging into V4Vapp using brave browser and the keychain extension, and no joy there either.
I see the problem: go to v4v.app not lnd.v4v.app (maybe you have that bookmarked?)
I'll try to stop that working or redirect it to v4v.app (you can click that link here).
Thanks, I've put in a rule to permanently send lnd.v4v.app to v4v.app without users doing anything, hopefully that fixes this.
Unfortunately that hasn't fixed the issue for me using v4vapp with keychain.
The steps I've taken since last msg are:
Changed to using v4v.app instead of lnd.v4v.app, plus I cleared all my caches before trying with v4v.app.
Tried using brave again with v4v.app... clearing caches and taking shields down etc
I tried downloading the app, and same error unfortunately @brianoflondon :(
I even tried removing the keychain extension from my browser and re-downloading it and firing up a new instance of keychain.
In all instances it returned the same error.
I am really sorry, I think there was a setting I failed to change. Just fixing it right now. Two minutes.... I'll post again when I think it is fixed.
I really hope this is fixed now. Sorry for what you had to do. My fault.
Cheers Brian.
It is working now, confirmed just signed in to v4v.app.
There are a bunch of people on ur latest post on the @brianoflondon account about v4v with the same issue they've highlighted in the comments. Could be worth letting them know it is fixed now.
Thanks again 👍