userofgos DeletedUser368 same happens to me, I see the full page for a millisecond before i get a white screen that says "Can't open page: Restart Vanadium or Restart your device". First time seeing this screen
de0u @DeletedUser368 @userofgos Can you report which GrapheneOS build number and which Vanadium build number? userofgos Which device model?
userofgos de0u Latest 2025071900 build on Pixel 8a with Vanadium build 138.0.7204.168.0 I've visited the site before and had no issues, but that was probably a month or two ago
DeletedUser370 This is a known issue which was reported on the Vanadium issue tracker three weeks ago. Here's a response by a GrapheneOS developer: This sounds like the site doing something like incorrect header checks to deter bots. Vanadium puts placeholder values from the Chromium frozen user agent string as the client hint headers. Could be something like that wrong with the site.
de0u DeletedUser370 When I go there the Vanadium tab crashes, as in "Aww, Snap! Something went wrong while displaying this webpage". Vanadium 138.0.7204.168 GrapheneOS 2025050700 Pixel 6a
argante DeletedUser370 It would be nice and more expected for the server to crash, not the Vanadium, as the browser must be resilient to such errors. If it's a memory error, it could pose a security risk.
raccoondad argante as the browser must be resilient to such errors It is not, if a fatal error were to happen, the isolated browser process would simply crash. Its not designed to keep going, its just designed to be stable.
de0u Based on a blip in the GitHub issue I think it might make sense to check back on whether this is still broken in around a week.
de0u The Vanadium issue was just closed, so it still seems to me this is likely to be resolved in a matter of days.
Titan_M2 Should be fixed with https://github.com/GrapheneOS/Vanadium/pull/851/files/29c275a2b4f836268acd16feb9dbb4b66625ec0f#diff-42ece0e15ed014df66c3af96019aedb77a4cb106ae1dbfc1b8deb02b8bc43e78
Overlay1404 Titan_M2 Is this bugfix out yet? I am on Vanadium version 138.0.7204.168.0 on my pixel 7 and still have the issue.
Titan_M2 Overlay1404 It will be fixed once 138.0.7204.168.1 comes to stable channel, or you can try it early on alpha/beta.
userofgos de0u thanks for the reminder. I just checked and it is now fixed. Great work GrapheneOS devs!