It was indeed the same version. I have also copied the actual .jar file from the client to the server to double check, but I still have the same issue. Both are running the version 1.7.2+1.21.1.

Someone using a dynamic DNS may not have access to a wildcard domain.

For example, if someone wants to use their hello.duckdns.org domain with more than one service, including Send, they could configure it this way:

services:
  # Caddy and other extra services

  redis:
    container_name: redis
    image: redis:alpine
    restart: always
    volumes:
      - send-redis:/data

  send:
    container_name: send
    depends_on:
      - redis
    environment:
      - BASE_URL=https://hello.duckdns.org/send
      - REDIS_HOST=redis
    image: registry.gitlab.com/timvisee/send:latest
    ports:
      - 1443:1443
    restart: always

volumes:
  send-redis:

At the moment, the workaround is to use one of their 4/5 free entries left with that specific dynamic DNS provider, but it would be even better if all services were able to play nice with each other.

Nato Boram (45925755) at 21 Apr 21:00

... and 10 more commits

Nato Boram (8adabf25) at 21 Apr 21:00

... and 1 more commit

Nato Boram (9ba902ca) at 21 Apr 20:59

Yeah sorry about that, been a bit busy with work and other projects.

I enabled a setting that should've changed the filenames to be deterministic (even though it makes the build depend on Git but whatever). I'm not sure if it makes the build itself deterministic. I know I said I didn't want it, but I'm really curious about having it set up properly.

But then there's that I have to re-learn the whole thing about the fdroid server every time I want to validate my changes and I still haven't gotten around adding the changelog/pictures properly.

About the fdroid server, is there like a Docker image that I can pull/run on this repo without having to install anything?

Apologies, I didn't realize that Iris was the one giving this error message instead of Distant Horizons.

Check off each item in this list before submitting:

1. Check the FAQ to see if your issue has already been reported and has a solution: Problems-and-solutions

2. Make sure you are not using any mods on the incompatible list: Mod support FAQ

3. Check the existing issues to verify that your bug hasn't already been submitted: Issues

4. Upload Minecraft's crash report and/or log.
   Minecraft crash reports are located in: .minecraft/crash-reports
   Minecraft logs are located in: .minecraft/logs

5. Upload your Distant Horizons Config.
   The config is found in: .minecraft/configs/DistantHorizons.toml

6. Fill out the information below:

• minecraft version: 1.20.1

• Distant Horizons version: 2.0.2-a-dev

• Mod loader: Fabric

• Installed mods (list the smallest number of mods that you can use to re-create the bug): N/A

• Describe the bug:

In the screenshot, there are two error messages:

• One completely unreadable by Distant Horizons
• One perfectly readable by Iris

I would like for Distant Horizons to log its error message where Iris logs it so we can actually read it :P

• Steps to reproduce the bug:

1. Open the game with an incompatible shaderspack

Nato Boram (36ec1f37) at 15 Jan 02:58