Have been very much enjoying Palworld and some ESO
Demigodrick
joined 1 year ago
MODERATOR OF
Sorry, having real issues with the latest version of pictrs (the software lemmy uses to show images) needing way too much ram and breaking, not sure what the solution is at the moment but trying to get the server to be stable is quite a challenge. Will likely need to change server or something.
Edit: always breaks when I'm asleep too
What concerns me is the fact the dev has another game in early access that looks pretty similar to this one just without the pokemon in it. Reviews seem good though.
If only they'd just fix linux support :(
Might be worth deleting all site data from the browser too - I've seen comments on github that browser caching can make it appear you're logged out when if you refresh the browser it will show you logged in.
I've not had this been reported to me before but if it does affect anyone else please let me know.
Are you using a mobile app or the web interface? All I can think right now is try signing out, deleting cookies and signing back in.
It is :)
Just can't be beaten for price/quality at this scale
Takes ages to do this migrating malarkey! All done now though thankfully
It's still ongoing 😭 hopefully done soon!
So after the upgrade we pushed all our stuff to them (I can see our posts on hexbear site directly now) so with any luck everything has been fixed :) let me know if you see anything else not right!
So it looks like they're pushing to us OK, but we're struggling to push our stuff to them. I did just try to visit the site and got a 502 error so not sure if they're having issues over there?
This link shows a bit more detail and you can see hexbear under "failing instances". Lemmy.ml and lemm.ee have the same issue as us, and I'm sure others will too. So either Hexbear's incoming federation is broken or they've been offline enough for instances to automatically flag them as offline.
Will see if there is an easy fix for this, but hopefully the federation fix in 0.19.2 will prevent this from happening in the future (if this is what it causing the issue and not a config issue hexbear side).
Edit: feel like I need to expand in case anyone is curious. From what I can tell the issue doesn't lie with lemmy.zip which I've determined two ways, one being that we are receiving stuff from them just fine and the second being that other servers appear to be having the same issue with flagging hexbear as failing. The next retry scheduled appears to be tomorrow (12th) some 24 hours after the last try the server made. If successful, I assume our server will then proceed to send all updates to hexbear as will the other servers, but this is the first time I've seen federation broken this way around so I can't say for definite what will happen. I've reached out to a hexbear admin on matrix I've spoken to previously to see if they're aware of this. I don't really keep up with other server's uptime so not sure if they've been offline a significant amount recently? This might cause all the servers to flag hexbear as failing. Otherwise I'm not sure the cause of it. But I'm pretty confident that federation on lemmy.zip is working fine and this is a hexbear issue.
test
On the eve on Lemmy.zip turning one week old, and following requests from members of the community, I'm putting together a post to show how Lemmy.zip is being run, the resources taken up in the back-end and the general day to day issues I've come across and resolved.
Hardware
Firstly, the setting up of Lemmy.zip.
Lemmy.zip (the domain) was purchased on Google Domains (apparently now sold off to squarespace?), and I have the domain for two years.
Secondly, the cloud platform is Hetzner Cloud. The server is based in Falkenstein, Germany. The server "name" is CX21 - Its an intel CPU, with 2x vcpus, 4GB of RAM, a 40GB SSD and 20TB of outgoing traffic.
After setting up SSH, I followed the Ansible guide to set up Lemmy, which got the instance set up pretty much instantly. Great success.. or so I thought!
Setup
The first thing I did was try federating with some other instances, which appeared to work straight away. Great. I tried some of the settings, added a logo, turned on user registration and email validation, added a site bio etc. Then I tried logging in and out. Oh no. I couldn't log back in with the Admin account, because email verification was turned on and I hadn't verified my email! Now, I know how to fix this via SQL commands, but at the time I had no clue. I also wasn't receiving any emails from Lemmy.zip. After some googling, it turns out Hetzner blocks port 25, which is the default postfix port (postfix is the piece of software that handles emails). So now I was locked out with seemingly no way to get back in. Whoops. So I went and deleted the server and started from scratch. I reinstalled Lemmy, set up the instance again and made sure email verification was off this time. I posted in a few places about the server, and suddenly people were joining!
The next step was to get email working. I did try SendGrid for emails first, who immediately refused to verify me and still, a week later, have not replied to my support request.
Next I tried Mailersend, who had quite a complex validation but did finally approve me. Then I had to figure out how to get the server to send emails using the Mailersend details.
After a couple of hours of testing, it turns out you only need to add the details to the lemmy config.hjson file, and you don't need to alter anything in the postfix container. I re-uploaded Lemmy, set email validation to true, and created a test account - boom! Email received.
For the most part, that was the first 24 hours done. I think by the end of the first day we had ~20 users, which I was really excited about.
Stats
As I'm typing this, we have 369 (nice) users, which is incredible. At one point, we even made it onto the recommended servers list however we've since been knocked off the list due to the uptime dropping after I've had to restart the server a few times. Still, another moment I was really proud of.
Most of the week has been quite smooth in all honesty, until today when I had a few reports that users couldn't register or log in to their accounts. It took quite a while to track down the issue, as the logs were not really giving anything away. Finally, I saw a line in the log which said api_routes_websocket: email_send_failed: Connection error: timed out
(this literally took me 3 hours to find this one line - tip, set logging level to warn and not the default info if you want any chance of finding errors in a busy instance!)
With a bit of googling, I was able to check my connection to the Mailersend smtp server and noticed that the telnet connection was timing out, which indicates that port 587 is being blocked somewhere in the chain. I have emailed Mailersend support but being a Saturday i'm not expecting a response for a while.
Before Mailersend stopped working, here is what the email stats look like:
You can see the expected tail off as Reddit opened back up, but then you can see emails drop to 0.
So with some frantic googling, I've switched (hopefully temporarily) to another provider, and emails are working again. Phew.
In terms of server performance, have some fancy graphs:
Server performance over the last week. The three big spikes relate to me doing something intensive on the server, rather than anything Lemmy is doing. Usage is mostly around 50% which is great, and gives us lots of growing room still.
Here are some other graphs to look at:
Live server usage as I'm writing this
Live network usage
Storage space used:
Storage used out of the 40gb - 36% used.
There was an issue with the pictrs container (the software that uploads/manages photos) writing a log that was about 7gb in size before I noticed. That has been fixed with a rotating log file rather than one big file.
Other stuff
Thought I'd add some stuff I've liked from the last week. Firstly, if you haven't already subscribed to the Starfield community and have an interest in the game, I urge you to do so.
A community I've quite enjoyed too is Dad jokes - definitely worth checking out if you want a laugh.
End
Hopefully thats been interesting for people - if there is anything you'd like to see more on, let me know. Happy to add more detail (where I can!)
Anyone is welcome to send me a message on here, I have no issues talking more privately. I have also set up an email address ([email protected]) for anyone who is locked out of an account or needs to share personal details and isn't comfortable using this platform to do so.
17
Starfield’s system requirements are up, wants a GTX 1070 Ti and 125GB SSD space at minimum
(www.rockpapershotgun.com)
18
Starfield Has Fewest Bugs In Bethesda History If It Launched Today, Microsoft Says
(www.gamespot.com)
The review score is already dropping on steam, I wonder if this will encourage them to reverse/fix the drm. Interesting to see they've already tried this and it didn't work, wonder why they're trying again on a different title.