I am hesitant to say that I have good news or that I have fixed anything… I honestly don’t know if there is anyone left still using this site after all the problems we’ve had.
That said, I noticed that there were some very recent (as in yesterday/today) commits to the development branch of kbin that look like they address the issues that fedia has been experiencing. I moved fedia to the development branch and reloaded some things, and so far, no error 500’s.
But, caveat emptor, we are on the development branch of early-in-its-lifecycle open source software.
I’ll keep an eye out and comment back if I notice anymore 500 errors. They were absolutely rampant over the last few days, but things seem all right currently.
It’s funny you mention “if anyone is still using this server” because of the technical issues. I would hope anyone coming to Kbin in general has their anus prepared for technical issues given that it’s an early in-development site, as you say.
This brings up a good point about the Fediverse, and how there’ll be different perspectives on it. I’m sure some have jumped ship because other instances are operating more smoothly, but from all your hard work, correspondance, and word of mouth from other Fediverse users I feel like I can trust your integrity and willingness to get the instance to a good place.
I’m willing to wade through technical issues a good deal because I feel that unless you throw in the towel, you’re gonna do what needs to be done, and that even if you did throw in the towel you’d keep us posted and that your reasons would be genuine. It’s like the difference between working at a large, stable company with faceless, questionably motivated masters, and working at a small, independent company whose future is not guaranteed, but you can understand the scope of what’s going on, and are able to openly communicate and understand your employers all the way up the chain.
I’m extrapolating all of this purely from not very much information, and I could be wrong, but my gut feeling says that I can trust your captaining of the ship, hopefully others feel the same.
These instances are a commitment I make to the community. That’s one of the reasons fedia was really bothering me - I don’t want to pull the rug out from people who are using the service - and so long as it’s being used, it’ll be here.
Yay, Jerry, you are awesome! It was working somewhat better (but still many 500s, could at least browse the main thread listings) since the updates a couple of days ago, and now I can’t get it to fail at all. Hopefully it’s fixed. Appreciate all the effort you have put into this, really liking the kbin experience so far.
Thanks. I am cautiously optimistic. I thought I had it fixed at least half a dozen times in the past, but it looks good so far.
I think I’ll switch back to Fedia for the time being, I mainly sought after kbin since everyone was flocking to it. But now knowing more how the Fediverse works, I think I’ll return here.
Found my first 500 error, at this URL: https://fedia.io/m/196@lemmy.blahaj.zone/t/48041/rule-mp4
thanks - will investigate
@jerry I think it might be all posts from 196@lemmy.blahaj.zone. Checked on kbin.social, works fine, but on Fedia I get a 500 error when visiting the magazine.
ETA: I also get a 500 error when trying to message a user from a different instance, even on the same platform (fedia.io -> kbin.social). This seems to be a platform bug, as trying to message this account from my kbin.social one results in me getting sent to home.
I’m now getting a 500 on https://fedia.io/all and on https://fedia.io/mod/microblogMy subs (where I’ve been spending most of my time), and the main microblog feed are working fine. Odd.
Edit: my personal subs list page seems to be doing this too: https://fedia.io/settings/subscriptions/magazines
Happy surprise with the WPA support as well. I really like them on a desktop, no losing track of windows, no extraneous UI elements, notifications identify the APP instead of just the browser.
Next feature I’m hoping for; ablobcats. :-D
Looking good so far, thanks for installing the update!
Ooh. That’s why there’s some some UI changes.
But, caveat emptor, we are on the development branch of early-in-its-lifecycle open source software.
Living dangerously, eh? You gotta do what you gotta do.
All I can comment ATM is that I’m no longer having the HTTP 500 erros I reported some days ago. Instead the issues I have now seem to do with federation: kbin magazines I’m suscribed to in other servers seem to not be updating (I get a message in Spanish that in English probably translates to something like “warning: this federated magazine is not complete. Explore the full content at [remote magazine link].”). Meaning I can’t ATM interact with magazines not in fedia.io since eg.: the posts or comments I want to reply to are not here.
Which leads me to a question I’ve always had about kbin model of federation but didn’t know how to put in words until now: my current understanding is that “federation” is actually the local instance working on an archived copy of the remote instance content and then sending the new content to be synchronized, yes? If so, is there an alternative model or configuration for federation that actually fetches the remote content when it’s going to be used rather than local users working over potentially incomplete copies?
I’m getting very “git rebase memes” from the current model, so I thought to ask.
My understanding is that when an instance subscribes to a magazine or community, the instance is effectively subscribing to updates and so the local cached copy is kept up to date. That, of course, breaks down when there are issues with federation. I do wonder: are you seeing this with all non-local magazines?
It seems that there is still some problem with certain lemmy instances. For example, lemmy.ml actively blocks kbin based instances (like fedia) and so I don’t think the magazines (lemmy calls the communities) coming from that instance are being updated.
I’m not seeing this with all non-local mags, but I’m def seeing it with all non-local mags that I’m subscribed to. I first thought it was a problem with subscription and tried desubbing and subbing again, but it doesn’t seem to have an effect.
It’s not a very breaking problem when it comes to threads, but it is when it comes to comments, because sometimes even if a thread (post) is mirrored, it’s incomplete and thus I cant participate in a specific comment tree.
I’m getting a 500 error loading All now. Subscribed is still working
Is fedia.io supposed to be fixed now? It surely is not working well for me. I came back to check after a hiatus of a few weeks.
Seems to be working today after your changes. Yesterday there was nothing but 500 errors!
Hey Jerry - I signed up on the 18th (same username) and validated my Email, but getting a “Your account is not active.” error on login. Any ideas?
Ok. It should be working now.
Working - thanks!
Odd - I will manually update the user record
did you change all the .env passwords/secrets since they were leaked through the symfony profiler? For example the username/password of the db
I have discovered that the vast majority of my 500 errors have gone away after removing the PWA version off my windows machine. It was using MS edge. Using.firefox, even with highest security settings and ublock origin.
I noticed.first.that in the pages header that magazine was not showing as an option. This sent me.down a.rabbit hole of messing with Edges settings and finally giving up on it and resorting to removing the PWA version.
Once I did that, the 500 errors stopped. Now I only get a 404 trying.to open my profile.
I found/fixed the issue with your profile getting a 404.
If you find any repeatable 500’s, please let me know.
Appreciate it. Although more 500’s popping up. Posted on the.June 29 update thread.
It’s more instances of a problem I thought was fixed: magazines, posts, comments, and users can have associated images. For some reason, kbin thinks it received and created a record in the “images” table, complete with a unique record ID, and associates that image ID with the magazines, posts, comments, and users as appropriate. For some reason, though, that image record doesn’t actually get created. When kbin goes to render a magazine, post, comment, or user, it sees that there should be an image associated and tries to look up the image to get the file name - that query fails and kbin doesn’t elegantly handle that, so an error 500 results any time that happens. I have to fix it by running a series of queries that null out missing image IDs. The bad part is that I am no longer seeing errors that are causing that behavior, so it’s more tricky to debug the remaining issues now, but I am working on it.
