Skip Navigation
Lodion Lodion πŸ‡¦πŸ‡Ί @lemmy.click

Main account is here

Posts 4
Comments 39
Ways to contribute monetarily?
  • Each instance admin will do their own thing. Check the sidebar on the front page of your instance, usually it would be mentioned there.

    To support development, click "Join Lemmy" at the bottom of the page, then scroll to the bottom. The devs have several methods to accept donations.

  • Instance relocation
  • I didn't, I spun up an entirely new instance.

  • Instance relocation
  • Nah, part of the playbook sets up the initial Lets Encrypt certificate... so DNS needs to point to the new VPS. And the hostname needs to match the existing instance as it is referenced in the database.

    Doesn't matter now anyway, I went a different route :)

  • Expressing concerns about moderation policy on lemmy.ml
  • Yeah, could do without the straw man arguments and deflective non-answers.

  • Instance relocation
  • Thats what the "docker-compose down" is for in the second step :)

  • Instance relocation

    I'm planning to move my instance to a new VPS provider that will allow me to scale more simply.

    Has anyone done this already and can sanity check my plan? My current setup was spun up using the ansible playbook here.

    Current plan is:

    Lower DNS TTL to 60 seconds (already done)

    Shutdown on current VPS: docker-compose down

    backup /srv/lemmy/<instance>/ and copy to new host

    sudo tar -zcvpf backup.tar.gz /srv/lemmy/<instance>/

    scp backup.tar.gz user@newhost

    update dns A and AAAA records, wait 1 minute, verify DNS has updated

    run ansible script

    Shutdown on new VPS: docker-compose down

    restore backup to /srv/lemmy/<instance>/

    Startup on new VPS with restored DB etc: docker-compose up -d

    test

    destroy old VPS

    Increase DNS TTL to 86400

    Anything I've missed? :)

    8
    Now Diablo 4 Is Out in the Wild, the True Horror of Its Costly Microtransactions Has Revealed Itself - IGN
  • I've only reached level 23, but have been thoroughly enjoying it so far. Usually end-game is the real test, but by most reports finishing the campaign is ~40 hours of gameplay alone. Given the hundreds of hours I sank into D3 it was an easy buy for me.

    edit: also the in game shop is totally ignoreable. Currently it isn't shoved down your throat, you have to go looking for it. Given it is 100% cosmetics, I'm not fussed by it.

  • Opinion on enabling email verification?
  • I've found email verification is finnicky to say the least. The Lemmy UI has some issues with users being stuck with spinning icons at various points for a start.

    In the back end... email is a pain. If you're using a public cloud VM and using the Lemmy provided docker/ansible postfix image, your users are unlikely to receive the verification emails as your server's IP address is likely n a DNSBL somewhere.

    If you use a third party SMTP service you may have more luck... but even then you'll likely have issues.

    I've disable email verification for these reasons, and rely on the answer to the signup question to vet applicants.

  • [SOLVED] Help with Lemmy setup
  • Thats a different issue to what I encountered. For me the nginx docker config had a reference to the host nginx config... I had no nginx installed so "docker-compose up" failed.

  • Federation issues
  • Then yes, as I said... no users on sopuli.xyz have subscribed to your community yet: [email protected] - 0 subscribers

    Other replies here have provided more info :)

  • Federation issues
  • Content for communities you've created on your instance will only be visible on other instances if a user there has subscribed to the community.

    Or do you mean yours posts to communities homed to other instances do not show up?

  • User list?
  • In the UI? Not that I know of. From the database... sure:

    docker exec -it <instancename>_postgres_1 sh

    psql -U lemmy -h 127.0.0.1 -p 5432 -d lemmy

    SELECT * from local_user;

  • [SOLVED] Help with Lemmy setup
  • If your VPS is purely for Lemmy, I'd suggest blowing it away and using the ansible playbook referenced here. I found the current docker-compose does not function, there are broken references to external nginx configs.

  • Would love a mobile app, at some point.
  • As others have said, Jerboa is for android... I've heard mention of "mlem" for IOS, but have not seen it myself.

  • lemmy.ml is overloaded, use other instances instead
  • Sure, its a bit wordy... lacking in images with step by step instructions. If I had time I'd put something together with screenshots and figure out git and submit a pull request... maybe eventually.

  • "Show Context" link icons confusion
  • The icon on the left is "context", on your home instance. On the right is the "fediverse" link, which takes you to the home instance of the poster.

    Basically the same thing, one is local the other remote.

    At least that is how I've come to understand them.

  • Following remote communities is hard.
  • ..that would defeat almost the entire point of being federated and decentralized.

  • Diablo IV is the fastest selling Blizzard game of all-time
  • Surprisingly... its better than I had hoped for. I'm ~6-8 hours in, level 23 or so... and its been great.

  • test

    test

    0
    Lemmy Support @lemmy.ml Lodion πŸ‡¦πŸ‡Ί @lemmy.click

    Admin user email verification

    I’ve hit an issue with Lemmy. Initial startup was fine… I created my admin user and logged in. Then I created this account.

    Third account I went to test with failed to login… then my other accounts also failed, so I rebooted.

    Now when I try to log into my admin account, it just spins forever. Checking logs, I see this:

    lemmy_server::api_routes_websocket: email_not_verified: email_not_verified

    Can anyone tell me how I can manually flag my admin account as having been email verified already?

    18

    Admin user email validation

    I've hit an issue with Lemmy. Initial startup was fine.. I created my admin user and logged in. Then I created this account.

    Third account I went to test with failed to login.. then my other accounts also failed, so I rebooted.

    Now when I try to log into my admin account, it just spins forever. Checking logs, I see this:

    lemmy_server::api_routes_websocket: email_not_verified: email_not_verified

    Can anyone tell me how I can manually flag my admin account as having been email verified already?

    0