No internet connection
  1. Home
  2. Issues

Approving comments on-page fails

By Michael Lynch @michael
    2026-01-04 13:56:28.371Z

    I'm seeing failures from TalkYard when I try to moderate comments on this page:

    https://refactoringenglish.com/blog/2025-hn-top-5/#comment-2

    I'm logged in as admin, but when I try to approve comments, I get this:

    Error 403

    Please log out and log in, to get a complete session id —
    this endpoint, /-/moderate-from-page, requires the HttpOnly part of the session id [TyEWEAKSID_]

    Reply
    • 11 replies
    1. Michael Lynch @michael
        2026-01-04 13:59:41.448Z

        Something's wonky with my session. It shows I'm logged in on the on-post comments:

        But the "Admin" link is broken, as it points to https://refactoringenglish.com/-/admin/review

        My profile links to https://site-1luhlxy7n7.talkyard.net/-/users/mtlynch/activity/posts but that shows me as not logged in:

        Reply
        1. In reply tomichael⬆:
          Michael Lynch @michael
            2026-01-04 14:01:58.533Z

            I was able to moderate via https://site-1luhlxy7n7.talkyard.net/-/admin/review

            I'm also noticing that my domain has switched from my previous https://comments-for-refactoringenglish.talkyard.net to https://site-1luhlxy7n7.talkyard.net

            Is that intentional?

            Reply
            1. KajMagnus @KajMagnus2026-01-05 10:10:26.287Z

              my domain has switched from my previous https://comments-for-refactoringenglish.talkyard.net to https://site-1luhlxy7n7.talkyard.net

              Yes and no. Google Chrome sometimes thinks that comments-for-some-website.talkyard.net is too similar to some-website.com and shows a phishing warning. And I think it happens more often to people who visit one's site infrequently, so it's not easy to know how often it happens. That's why I switched all new sites to https://site-<site-public-id>.talkyard.net. (But if you're admin, Chrome knows you've visited the embedded domain already so I think it doesn't show any warning.)

              But this change affected you now, and not say 1 year ago, hmm I'm not sure. You didn't happen to make some configuration changes on your side recently? I think it was some month(s) ago I upgraded the server last time.

              I can write some changelogs for the recent versions, so I'll better remember what has changed. (Didn't do last half a year or so)

              Sorry for the confusing error messages and surprising new address. (Blog visitors shouldn't see this address, unless they inspect the HTML)

              Reply
              1. Michael Lynch @michael
                  2026-01-05 10:27:01.283Z

                  I don't believe I made config changes recently. I don't get a lot of comments on that site, so it may have been a while since I last approved a comment there.

                  Comment approval still works as expected on mtlynch.io.

                  Reply
                  1. KajMagnus @KajMagnus2026-01-05 12:19:27.114Z

                    Ok,

                    Comment approval still works as expected on mtlynch.io.

                    That's because you use a custom domain: https://comments.mtlynch.io rather than using Talkyard's auto-generated comments-for-... (which now instead is site-123456789).

                    Maybe I should change the instructions so everyone is recommended to use a custom domain (e.g. comments.ones-own-domain.com). Because these site-123456789.talkyard.net addresses look pretty weird, right. And Google Chrome's algorithms for figuring out if a site is maybe a phishing "clone" of another, seem unpredictably trigger happy.

                    Reply
                    1. Michael Lynch @michael
                        2026-01-05 20:00:45.725Z

                        Okay, thanks! I switched to comments.refactoringenglish.com, but I'm still seeing issues.

                        The "Admin" and "Discussions index" links are broken:

                        Reply
                        1. KajMagnus @KajMagnus2026-01-06 05:28:59.629Z

                          Ooops, looks like regression(s), I'll have a look

                          Reply
                          1. KajMagnus @KajMagnus2026-01-07 20:13:57.388Z

                            Fond it, fixed in the upcoming version, which will be released ... at the end of next week I'd think. Thanks for reporting

                            (Seems I added these bugs when I did some refactoring related to embedded forums)

                            Reply1 Like
                • In reply tomichael⬆:
                  KajMagnus @KajMagnus2026-01-07 20:20:34.910Z

                  I think the Please log out and log in ... /-/moderate-from-page is a separate issue — seems I've made an endpoint too strict, will fix in the upcoming version too.

                  Reply
                  1. In reply tomichael⬆:
                    KajMagnus @KajMagnus2026-01-22 12:29:35.200Z

                    Now these two problems have been fixed (that is, 1) embedded comments admin link broken, and 2) approve-from-blog-comments-discussion broken), should work for you now :- )   (sorry it took a bit longer, I fixed some other problems too in the same new version)

                    Reply
                    1. Michael Lynch @michael
                        2026-01-22 20:08:18.900Z

                        Awesome, thanks!

                        Reply
                      • Progress
                        with handling this problem
                      • @KajMagnus marked this topic as Started 2026-01-07 20:14:25.904Z.
                      • @KajMagnus marked this topic as Done 2026-01-24 16:21:14.304Z.
                      Reply (discussion)