[-] [email protected] 2 points 1 hour ago

It's a known issue - I have been working with @[email protected] for a while now to resolve. I think we now understand what is happening under the hood, but not yet why it is happening.

[-] [email protected] 2 points 2 days ago

lemmy (running on infosec.pub) does support both post formatting and previews. mbin supports post formatting, but not previews (yet)

[-] [email protected] 2 points 2 days ago

There were lots of changes around the same time. I removed fedia.io from the CDN a few days ago though didn't announce it, yet the errors continue.

[-] [email protected] 3 points 4 days ago

What works for me on both mastodon and Lemmy is a free text question: why do you want to join?

The user enters whatever they like and it goes into a moderation queue. Both lemmy and mastodon send me an email when a new account is ready to review.

I read the response and choose to whether to approve their account. At the moment, spammers are really bad at answering the “why do you want to join” questions.

[-] [email protected] 4 points 4 days ago

Howdy! Mbin (and lemmy) are very different things. It’s sort of like the difference between Twitter and Reddit. You can sort of interact back and forth, but to get the full experience, you have to either be on a lemmy or mbin (or piefed) instance.

[-] [email protected] 3 points 4 days ago

it's hard to make a blanket statement, because it depends on the details of the application. CSRF attacks are definitely real and common, but using csrf tokens isn't critical in every application. For example, I think we have CORS headers enabled, I don't think we have functionality that allows embedded iframes, but we do allow links - if we have administrative functions that can be triggered solely with GET parameters, then someone could trick an administrator into doing something that caused damage by clicking on a link in a post. The only one that would obviously work that I can see is "logout", which would be annoying, but not world ending, and would work for everyone, not just administrators.

[-] [email protected] 2 points 5 days ago

ok - I just had it happen again while looking at logs. interestingly, there was NOT a CSRF log when that happened. There were a bunch of other errors, but enough that I could look through all of them and see that they were all related to activitypub issues - signaturevalidator and the like

[-] [email protected] 1 points 5 days ago

Indeed. I am trying to get it to happen again now that I’ve got the logs filtered down to a manageable level.

[-] [email protected] 1 points 5 days ago

I do not have 2fa turned on right now.

[-] [email protected] 2 points 5 days ago

Most interesting: the problem had only been happening on MS Edge on my laptop. I have been using safari on my phone without issue. Just a bit ago, i refreshed the page and now every time I revisit the site, I have to log back in, just like on Edge. It’s like the old session expired and the new ones aren’t sticking. I’ll try FF on my phone.

Note: even in the time I started typing this reply to when I hit the “add comment” button, I got logged out

[-] [email protected] 3 points 5 days ago

This annoys me about the fediverse - people take a chance on coming here and then repeatedly get left in the dark when their instance is shut down. That's why I was so very happy when you and others helped me get fedia.io back to healthy.

29
submitted 5 days ago by [email protected] to c/[email protected]

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 ([email protected]) and I’ll get an account created for you in the mean time.

[-] [email protected] 4 points 6 days ago

I moved fedia.io away from fastly. I have a nagging feeling it has something to do with fastly. Can you let me know if you continue to see this?

23
submitted 2 weeks ago by [email protected] to c/[email protected]

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.

1
submitted 1 month ago by [email protected] to c/[email protected]

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.

1
test2 (fedia.io)
submitted 1 month ago by [email protected] to c/[email protected]
3
submitted 1 month ago by [email protected] to c/[email protected]
3
submitted 1 month ago by [email protected] to c/[email protected]
16
submitted 1 month ago by [email protected] to c/[email protected]

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.

11
submitted 1 month ago by [email protected] to c/[email protected]

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.

18
submitted 1 month ago by [email protected] to c/[email protected]

The (relatively new) server that Fedia.io was running on, a Hetzner AX 162-R, died overnight. Hetzner tells me that the main board failed and had to be replaced. In the process of repairing, the raid set got corrupted and would no longer boot.

Every single AX 162 (R or M) I’ve rented from Hetzner has failed now at least once. This was the last one I had. It was on my to do list to move fedia.io to a Dell server with the same specs. I knew this was going to happen, but I didn’t get it done in time.

For those of you who have been following along, Fedia has been cursed from the beginning. The kbin software was a god damned disaster, and very fortunately the mbin team spent an incredible amount of time and patience to help me sort out the many problems, nearly all of which are fixed now.

Except for the random occurrences where federation breaks due to an as-yet-unknown bug, the main stability issue has been hardware. I have had excellent luck with Hetzner’s Dell servers, so I am hopeful that is now fixed as well. The challenge is that the Dell server is quite expensive ($350 per month) so I will be looking to find a more cost effective way to host fedia.io, given the very small number of active users.

15
submitted 3 months ago by [email protected] to c/[email protected]

I will be rehoming fedia.io to a less expensive server the afternoon of July 1 - exact timing is TBD. Downtime should last about 2 hours. The current server is quite expensive and donations are dwindling, which is normally ok, but I am losing my job and have to be a bit more frugal.

24
submitted 4 months ago by [email protected] to c/[email protected]

Yesterday, the fedia.io server locked up. I was able to reboot it remotely and it came up clean. After less than an hour, the server froze again. This happened several more times throughout the day. Unfortunately, there were no logs recording what happened, and nothing on the console - just frozen hardware.

I contacted Hetzner early this morning and they diagnosed the server as having a faulty motherboard. Hetzner replaced the board and rebooted the server, and so far the server has been stable.

I have had pretty bad luck with this particular model of server from Hetzner, so I do not have confidence that this won't happen again, and so will be looking to migrate to a different type of server that is hopefully more stable and less expensive (I am losing my job at the end of June, and so need to save all the cash I can).

21
submitted 5 months ago by [email protected] to c/[email protected]

Fedia.io had a few issues over the past 24 hours - sometimes working find till you click on certain posts, which result in an error 500, and other times just getting an error 500 no matter what.

The first issue I found is that amqproxy, which helps to reduce the load on the server between the queue runners that process incoming and outgoing posts and rabbitmq. I found this morning that amqproxy was consistently failing, despite there being no apparent problem. I bypassed amqproxy, since the server can handle the load fine without amqproxy. That seemed to work and things returned to normal. A few hours later, the site started responding with error 500 to nearly all requests. This happened because the database server ran our of connections. The 300 it was set to should have been plenty, but clearly it was not. I've set that to 3000 and so far, so good.

My apologies for the instability. I continue to learn the nuances here and will keep making the service more reliable as I go.

view more: next ›

jerry

joined 1 year ago
MODERATOR OF