I’m on iOS 17.1.1 using Safari. I also have Proton VPN enabled in the states but if I try to visit any page on the website I see this:

If I disable it, the page will load.

Edit: as per a comment, this may not be a VPN only issue.

Additional edit: Reddit has written an official post stating it was an issue after production code deployment and was reverted

    • tokyo@beehaw.orgOPEnglish
      10·
      10 months ago

      If you encountered it without a VPN, it would appear to not be based purely on VPN usage - which at the very least is good news for the privacy oriented.

    • SokathHisEyesOpen@lemmy.mlEnglish
      46·
      10 months ago

      It’s not a bug. It’s them running A/B tests to completely block mobile users that aren’t on the app. They’ve been implementing different versions of this for over a year now. They always lie about what it was. Actually they pretty much habitually lie about all of their tests and changes.

      • dreadgoat@kbin.social
        31·
        10 months ago

        https://en.wikipedia.org/wiki/Hanlon%27s_razor

        I got this bug on desktop, running chrome, with no VPN.

        This was, as most things like this are, just a pure dumb fuck-up by some guy putting things on prod without properly testing and staging. No need to put on any more tin foil hats than we already have, the incompetence is plenty reason enough to point and laugh.

        • nis@feddit.dk
          9·
          10 months ago

          Both can be true. The incompetence could have happened while trying to block mobile use.

          The amount of dark patterns pushing users onto the app has already established the malice.

        • Diplomjodler@feddit.de
          1·
          10 months ago

          If an internet corporation has a history of enshittification, it gets increasingly hard to clock up these kind of things to incompetence. While stupidity can certainly explain some things, it’s usually safe to assume it’s a bit of both

  • ZeroCool@feddit.chEnglish
    19·
    10 months ago

    https://www.reddit.com/r/ModSupport/comments/17vbyr8/whoa_there_pardner_error_message/

    Text:

    Hey all!

    It looks like most of you had difficulty reaching the site for about 5 minutes, but those issues should have subsided.

    During that time, you may have been shown an incorrect error message that read:

    Whoa there, pardner! reddit's awesome and all, but you may have a bit of a problem.

Make sure your User-Agent is not empty, is something unique and descriptive and try again. if you're supplying an alternate User-Agent string, try changing back to default as that can sometimes result in a block.

    To share some additional context on what happened - we pushed a bad code change in our tooling that resulted in a significant amount of users getting blocked without doing anything wrong. So if you happened to see that error message within the last hour, don’t fret! We’ve reverted the code change that caused this error and things should be back to normal very soon if they aren’t already.

  • Flax@feddit.ukEnglish
    18·
    10 months ago

    “whoa there, pardner! reddit’s awesome and all, but you may have a bit of a problem.”

    ----------------V---------------

    1000013915

  • eutsgueden@lemm.ee
    10·
    10 months ago

    Also started seeing this today while browsing on my work computer, which I believe utilizes a VPN.

  • ReversalHatchery@beehaw.org
    8·
    10 months ago

    Additional edit: Reddit has written an official post stating it was an issue after production code deployment and was reverted

    In their mind the issue was not the blocking of users, but that the users have started complaining. I bet they just reverted it so that they can bring it back slowly, after just checking whether it is effective at all

  • hedge@beehaw.orgEnglish
    7·
    10 months ago

    Looks like I can get to reddit pages via Libreddit with Mullvad up and running, if that helps at all.

    EDIT: And reddit via reddit too!

  • bermuda@beehaw.orgEnglish
    7·
    10 months ago

    I don’t have a VPN and I got this error too. It resolved itself after about an hour

  • noride@lemm.ee
    5·
    10 months ago

    Your VPN doesn’t have the ability to strip user agent strings on HTTPS requests, this doesn’t seem VPN related imo.

  • dcormier@beehaw.orgEnglish
    4·
    10 months ago

    I had this when using my corporate VPN. Disconnected and still got it. I thought maybe it was a bug that had to do with Firefox.

    A few minutes later I refreshed and it was all fine.