You can use the triple backticks for better rendering on lemmy:

imit_req_zone $binary_remote_addr zone=lemmydocker.genesis-radio.net_ratelimit:10m rate=1r/s;

server {
    listen 80;
    listen [::]:80;
    server_name lemmydocker.genesis-radio.net;
    location /.well-known/acme-challenge/ {
        root /var/www/certbot;
    }
    location / {
        return 301 https://$host$request_uri;
    }
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name lemmydocker.genesis-radio.net;

    ssl_certificate /etc/letsencrypt/live/lemmydocker.genesis-radio.net/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/lemmydocker.genesis-radio.net/privkey.pem;

    location / {
      proxy_pass http://0.0.0.0:8536;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header Host $host;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}

access_log /var/log/nginx/access.log combined;

Replied on your other comment that you deleted

Yeah so you’re just sending everything to the lemmy server itself, you don’t have the lemmy-ui frontend (which defaults to port 1234).

Look at the example NGINX configuration: https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/nginx_internal.conf

Notice how it sends different things to one of the two backends. You need this replicated exactly or it won’t work quite right.