I noticed that when I visit my profile page (https://fedia.io/u/ciferecaNinjo) while logged out, I get a 504 gateway error, but if I login then my profile page renders fine. It has been this way the past few days. If I view my profile from a logged-out browser while logged in in another browser, the logged out browser sees the profile fine. So to reproduce it would be interesting to visit anyone’s profile who is logged out.
Fedia is still having some stability issues. I set up some automation to detect the problem and then restart the services. If you were to look at that page while the services were restarting, you will see that error
ok - I took a bit different approach. Since I know what error in rabbitmq's log file is associated with things coming to a stop on fedia.io, I installed swatchdog and set it up to look for that word (which is, btw, "timeout"). I created a script that stops all the messengers, then stops php-fpm, keydb, and rabbitmq. Then it start rabbit, keydb, and php-fpm in order. Finally, it restarts the messengers.
I will be surprised if it works first time, so it may still crash again but I'll be watching
Hello, I have stopped seeing errors in general browsing, but today I am having some difficulty loading some of the most-commented threads. Not sure if this is related to the earlier PHP issues. Let me know if you'd prefer I report this on the Mbin GitHub instead.
Can you shoot me the IP address(es) you are assigned? I will see if there is some reason the firewall would be blocking them. Beyond that, I am guessing Orange is doing something to filter it
The recent version seems to cause PHP to off into space somewhat frequently. I am working to mitigate it - which will likely, at least for a while, require me to restart the services every few hours until we can figure out what the actual cause is.
Even on local ( see newest posts at /m/test ), images with alt-text (?) seem to trigger an upload failure.
I've also been having trouble with thumbnails not being generated on the lemmy-side of YouTube links I've posted -- which I initially thought was something on YouTube's end (they made some breaking changes recently) but maybe it's related to this instead?
The 403 was the planned response when you tried to DM any remote user, because federation of message was just not implemented. With v1.7.0 we implemented it and you will not get a 403 anymore
fedia
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.