stown

My man Louis Rossman needs to take a chill-pill and get some sleep. Dudes heart isn't going to last very long. Let someone else take the reigns for a while.

Automated money laundering.

You can do all of those things with wireguard as well... I'm not seeing any benefit to running Tailscale/headscale.

If you don't have a static IP then you will automatically have a dynamic one. You don't need to ask for a dynamic IP as that is the default. And I'm no idiot, I've used dynamic DNS services for for over 20 years.

If you're going to do that you may as well cut out the extra server/service and run regular wireguard.

Tailscale is a service that relies on a third party to facilitate the VPN connection between your client and server. It is designed for people who don't want to or cannot forward ports. Your server and your client both talk to the Tailscale servers and traffic is routed that way.

Dynamic IP is one that changes. I think you meant static IP.

Recently commented on a different post about setting up a VPN. Check out firezone

I don't recommend using Tailscale or anything that relies on a third party.

I can recommend firezone as well. Served me well before I decided to host my wireguard server on OPNsense.

I still miss the super easy client setup from firezone! OPNsense really needs to make it easier.

Where do we draw the line? Is a stone chiseled wheel considered technology and could I appropriately post a picture. How about a steam engine? I was under the impression that this community was for news and info about new and upcoming technology. If this is not the community for that could somebody point me in the right direction?

Check this GitHub link for instructions. https://github.com/LemmyNet/lemmy-ui/issues/1530#issuecomment-1605781461

Once I get home from work this afternoon I will post my docker-compose.yml which has an extra container that automatically deletes the database entry then resets it.

EDIT: Here is the extra container from my docker-compose.yml

  icon-fix:
    image: iconfix:latest
    command:
      - /bin/sh
      - -c
      - |
        sleep 10
        # Remove Site Icon - be sure to set your postgres password
        PGPASSWORD= psql -U lemmy -h postgres -d lemmy -c "UPDATE site SET icon = NULL WHERE id = 1;"
        # Refresh Site - replace example.com with your sites domain
	curl -f -sS -H "Host: example.com" http://lemmy-ui:1234 > temp.html
        # Reset Site Icon - Set your postgres password and replace the URL with one that points to your icon
 	PGPASSWORD= psql -U lemmy -h postgres -d lemmy -c "UPDATE site SET icon = 'https://example.com/pictrs/image/2cc85182-5739-4c86-b982-94fc913e80d3.webp' WHERE id = 1;"
    depends_on:
      - postgres

And here is the Dockerfile for building the iconfix image

FROM docker.io/postgres:latest
RUN apt update
RUN apt install -y curl

This is an issue that has been present for a long time but recently came back worse with the 0.19 update. It is caused by lemmy-ui failing to load the site icon and it typically happens whenever the the docker container is started/restarted while you have a site icon set. The only fix at the moment is to manually delete the database entry which contains a link to the site image.