The odd part is that it was running fine until the upgrade.
The odd part is that it was running fine until the upgrade.
I used the Lemmy-Easy-Deploy method but the catch is that I migrated from Google Cloud Free Tier to a paid server with another host. I have the backups so I can always restore from that if I really have to. I have an env file with the password that it should be using but I’m not sure how it was changed…
What Cloudflare API am I supposed to use?
You have more faith in people than I do…
Project Manager
Did you request him to a add the ones you want?
Definitely noticeable!
Also, the amount of communication here is AWESOME! Thank you for keeping us updated.
Thank you! I’m hoping this solves a lot of the issues!
It seems that my Hot feed has been stuck for the last day or two.
The US Coast Guard did NOT detect any implosions just as they said. It was the US Navy that detected it.
Whether or not that was communicated to the USCG, I don’t know.
Edit: now I see in the article- it was communicated on Sunday. But the USCG statement was still technically true. They didn’t detect an implosion.
I blocked them this morning. Didn’t want to but it was overwhelming.
THANK YOU!!! Ugh, this has been super annoying.
Everything about this is cool! It feels like an “internet” reboot.
Yeah, I have a kbin account and noticed the same thing. I keep going back and forth between the two. I understand why it’s implemented, but I’m not sure I entirely like the idea of having every favorite being visible to the public. At least they’re only visible on the specific comment/ post but not visible from the user profile.
I’m on lemmy.world and I can see the time and date your comment was posted and same for edited.
I couldn’t get my container started with postgress running but I had an idea:
I started the upgrade process with Lemmy-Easy-Deploy,
canceled out of it before it removed the containers,
ran
sudo docker exec -i lemmy-easy-deploy-postgres-1 psql -U lemmy -c "alter user lemmy with password 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'"
with the password set in my
env
file,then restarted the upgrade process. It’s running again.