Hi guys, I’ve dove into the klipper scene with my Neptune 3 and am having a really odd issue.

When I first got klipper/ Fluidd set up, I tried loading the interface in my browser (Chrome) and got an all white screen. At first I thought it just failed to connect, or the process wasn’t running, but then noticed the tab was named “Fluidd”. I spent an hour or two reinstalling things over and over before I decided to try a different browser (Edge). It loaded up just fine. I pulled it up in Firefox and spent a while configuring it. I had to reinstall the Pi’s OS a few times, but each time Fluidd came up in Firefox without issue but failed to load in chrome.

Now, suddenly, it is failing to load in Firefox, but continues to load in Edge. Below is a screenshot from my PC with all three browsers with the same address typed into the bar, with only Edge loading for some reason… Does anyone have any clue what could be causing this? It also loads on the Chrome app on my phone.

  • NickKnight@lemmy.worldEnglish
    1·
    8 months ago

    Call me mister suspicious if you like but I have had this exact issue daily with Chrome since they started complaining about adblocking. And wouldn’t you know it, the moment any form of adblock is disabled it miraculously does not happen. I can also fix it by clearing my cache every day and restarting the browser. I would start with those steps.

    • papalonian@lemmy.worldOPEnglish
      2·
      8 months ago

      Hey, sorry for not replying, I completely forgot - I tried disabling as blockers and all that jazz but nothing worked. I ended up deciding that I liked Mainsail’s UI more than Fluidd anyways so I decided to ignore the problem.

      I also initially suspected Chrome sticking it’s nose in my business as it started giving me nonstop warnings and blockers about turning on their safe browsing (every file, regardless of file type, was automatically being cancelled because they couldn’t “verify” it. I had to reconfirm every download), but then it stopped working on Firefox too, so I can’t blame them for this one. Silver lining: the issue got me to download Firefox, something I’d been meaning to do, and now I’ve jumped boats.