SO I wrote in a previous message about accessing Federation / comments for a self hosted blog: https://fukinsei.webfright.com
This still doesn’t seem to work, having read a post from someone unable to follow their blog when using NGINX. I too am using NGINX for the above url, but am able to follow / unfollow.
My problem of not being able to see my posts remains. Having previously experimented with removing federation / reinstating federation , the blog posted two posts to mastodon. Since then it has stopped posting other than the post count which is incorrect (11?) a and is still linked to mastodon. I have posted more than the post count indicates since reinstating federated? posts. Having followed my own posts on Mastodon I can see nothing other than two previous posts and I’ve changed nothing.
TL:DR, posts still not showing on mastodon,even though it states there are 11 posts, which is also wrong.
Thanks in advance for any ideas, I am using the docker install of write freely along with NGINX, all ports required have been set and have have all the standard settings, nothing exotic and I also realize that although I am following my own blog, my blog shows 0 followers??
This is likely on Mastodon’s end – there are a lot of little things that are off due to how federation works. For example, your blog may show different counts from what you actually see on Mastodon.
If you check your Subscribers page on WriteFreely, does your account show up? I just tested, and was able to follow / unfollow from our Writing.Exchange instance. But otherwise, as long as you’re following your blog from your Mastodon instance, posts should show up there.
Thank you for replying, no I’m showing 0 subscribers and I followed my own blog to test when I setup federation and thats the odd thing only two posts show up from that initial setup. I’m unsure if it makes a difference, but I’m using writefreely in conjunction with Nginx ( both docker instances), having looked at the .conf file there seems to be very little to play with in respect of this, but that’s not to say I have missed something.
Thank you for this and it might be the solution, but has also caused another problem…I changed http to https as I’m using lets encrypt through nginx proxy manager, but it throws up a 502 bad gateway. So at least I have a possible solution once I have worked out why its not working through https.
Thanks again the links now seem fixed and shows all urls are now pointing to https, rather than http. For some reason I had to swap out ports 8080 for 443 in the config otherwise i kept getting a 502 when ever I tried to use https in the config..and Nginx seems to be doing the rest, so, I’ll see what occurs with interfacing with the 'verse, many thanks!
As and aside, I swapped the ports back to normal as an experiment and it still works fine, my guess is there was some lag in the change in url from http to https??..anyway a big thankyou