Starting today, I noticed some of my comments and posts aren’t being visible to me when I am logged in. According to the RSS feed, logging out and checking it through an incognito tab, the posts are successfully posted on the instance and others’, however.

Take this post for example: https://compuverse.uk/post/822

Here you can see I am able to view my post:

But when looking at my profile, said post is not visible:

Same applies to several recent comments I have made. Am I missing something, or is there something wrong with the instance at the moment? When logging off, I can see the post just fine on my own profile:

This is also the case when using the Android client (Jerboa), and when trying to hard-refresh pages etc.

  • TopHat@compuverse.ukOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Actually, your suggestion might indicate something important. The domain of the instance did change, with the old one giving 404’s to get it off the list. Although Cameron did check the configs and didn’t find anything wrong with them.

    @[email protected] Worth to cross-post to the admin channel, with the context of having switched over domains?

    • Cameron@compuverse.uk
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Technically the domain of this instance didn’t change. This instance was setup from scratch, under compuverse.uk.

      However, a different instance did run under the same domain for a brief period of time, which was removed, and completely replaced by a brand new fresh instance.

      • PriorProject@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        It is possible that nginx or some other http proxy is forwarding requests via some borked virtual host or url rewriting config, such that requests are arriving at Lemmy tagged with the old name?

        Perhaps the affected user could clear some browser caches as well to ensure there is nothing funky going on in their specific browser.