Fedia Discussions

After I resolved the federation issue, I had to clean up a few things and so the site may have been unavailable for a bit. I'm done fussing with it and will keep an eye on it to make sure things are working.

IF YOU SEE PROBLEMS - please let me know. As far as I know, I've fixed all of the federation and error 500 issues we've had, so please don't assume it's just more of the same if you see them.

Thanks for your patience.

Fedia.io is sort of like she Ship of Theseus right now - I literally replaced nearly everything trying to get it back working.

The problem ended up being a silent out of memory error that php-fpm was running into. I had to increase the memory limit to about 10x what the docs require to get it to work, but once I did that, it works great.

I was only able to sort this out after @bentigorlich recommended I move the site to debug mode (which requires me to lock everyone else out). Once I did that, it started giving some useful errors.

My apologies for the amount of time it took to fix this. I learned a lot about php today.

Hi all. As some of you have reported, outbound federation to at least some other instances is broken from fedia.io. At the moment. I don't know why and I don't have any leads as there are no logs or other indications of what is going wrong, but I am working on it.

This is a test

Hi all. Several of you have reported problems with fedia.io not federating with other instances correctly.

The cause is that rabbitmq crashed, but not all the way. It crashed to the point where new connections would timeout, but the service was still running such that it wouldn't auto restart. I will be creating some automation to detect that proactively and restart rabbitmq if/when it happens again.

How user accounts work with the fediverse?? Can I sign in with my Fedia account on other Lemmy, Mbin etc instances?

#fedia

for two days, threads posted on fedia.io magazines apparently do not show up on lemmy > this does not only affect the poetry magazine, but also https://fedia.io/m/FloatingIsFun - i guess the same applies to other fedia.io magazines > i have already checked both lemmy.world and infosec.pub: no new threads show up

We made some changes a few minute ago that we hope fixes the problem. There may be some other lingering issues, but I am hoping the voting problem is fixed now. Let me know below if you continue to see that problem.

I tried to upvote this comment:

https://fedia.io/m/Brussels/t/1145402/Delhaize-and-Intermarche-loyalty-more-intrusive-than-Colruyt-but-Colruyt/comment/7061005#entry-comment-7061005

Got a page that simply said “Error”. That’s it. Not internal server error or a 500 error.. just “error”. Thought it’s worth mention since it’s possibly the first time I've seen such a generic and info-deprived error msg.

I'm noticing that my comments are not getting federated to (at least) lemmy.world, wondering if there's something going on with federation.

Edit: I'm guessing someone kicked something, because I'm seeing them over there now!

Until I implement a better system to screen out spammers, I will be closing registrations on Fedia.io. That’s not what I want - I’d like for it to be available for legitimate accounts, but the spam is off the hook.

Anyone seeing this can send me an email (jerry@infosec.exchange) and I’ll get an account created for you in the mean time.

When trying to register, I fill out a username, email, and password (copy/pasted from a password manager, so no chance of mistyping). I complete the captcha, check the consent box, click register, and... nothing. Page refreshes, but there's no errors displayed or anything. I've tried resetting my password, but I never get an email for that (I'm assuming because creating my account failed). I've tried different browsers, mobile and desktop, addblockers on and off, and get the same result every time.

All hail our new content delivery overlords

(the switch also caused a brief federation outage, which should be sorted now)

Hello everyone. Today, I moved fedia.io behind the Fastly CDN. This should make the site consistently fast for everyone, no matter where you are in the world. It'll also help with bandwidth usage and mitigate DDoS attacks.

There were a few hiccups as I set that up today - my apologies if you saw errors or broken images for a bit.
EDIT: I previously said that this was the first time mbin or kbin was put behind a CDN. That is incorrect. kbin.earth has been behind Cloudflare. Apologies.

Right now the default sort for threads is "Hot". Can I change the default somehow? I don't know if the option exists or if I'm blind, I can't find it anyhow.

Hi all. I've been having some problems keeping fedia.io running - at the moment, either the message workers or the php web server processes are dying after an hour or so and I have to restart everything. I have been working with the mbin team and installed some updates that we hoped would fix the problems, but no luck. I am going to work on a cron job to automatically restart things once an hour. The down side, is that you'll likely see some error 500's if you happen to hit it when the processes are restarting, but it should happen quickly and refreshing the page should make it work again.

As the linked post demonstrates, if you enter a link like this:

[mail2tor](mail2torjgmxgexntbrmhvgluavhj7ouul5yar6ylbvjkxwqf6ixkwyd.onion)

mbin thinks it’s something else. Indeed it’s not a URL due to the lacking ‘scheme://’, but it’s bizarre what it does with the links.

Since SSL is not generally needed for onions, every link would require some effort to know whether it should have a scheme of http:// or https://. Mbin should just pick one of those schemes arbitrarily.. certainly not whatever it’s doing at the moment.

My ISP is Orange Poland

• It's GSM 4G/5G branch of Orange I use on my cellphone.

I can open literally any other site, including other kbin/mbin/lemmy instances.

It's probably already on your radar but I didn't see a thread* about it so I figured I would mention it.

Seen 502 when trying to load the main page, and on occasion when viewing my feed on mobile web the page would transition to a 503 or 504 error seemingly without my input.

After creating a new photo post to https://fedia.io/m/lemmyshitpost@lemmy.world it seems to automatically convert it to a thread post and it loses the photo, figured i'm not the only one having this issue

*edit: Jerry worked with the mbin developers and instituted a fix. Thanks Jerry!

Shortly after upgrading to Mbin 1.7.1-rc1, php ran out of workers. I dramatically increased the limit. It isn’t clear to me why that happened and if it’s related to the upgrade or just coincidental. My intuition is that it’s related, but I have no evidence.

Hello everyone. I just upgraded fedia.io to mbin 1.7.1-rc1. One of the notable changes is that mbin is deprecating mercure, which is the component that provided streaming updates. As such, you will have to refresh the web page to see new posts and comments.

I tried to DM a Lemmy user. This URL was associated to the mail icon:

https://fedia.io/u/@Servais@discuss.tchncs.de/message

That gives a 403 forbidden. I use Tor but neither fedia nor discuss.tchncs.de are tor-hostile. So I doubt Tor is related.

I have to say apart from the above issue, fedia has been working smoothly lately. I’m glad the internal server errors that plagued the system have apparently been resolved AFAICT.