I cannot get a certification

I am as confused as you are orisis, i defenetly fucked up this one haha. Is it just easier to start over, how i would that then.

sudo netstat -nap | grep docker
tcp        0      0 0.0.0.0:2283            0.0.0.0:*               LISTEN      1997/docker-proxy   
tcp6       0      0 :::2283                 :::*                    LISTEN      2012/docker-proxy   
unix  3      [ ]         STREAM     CONNECTED     8152     1262/dockerd         
unix  3      [ ]         STREAM     CONNECTED     8763     1262/dockerd         
unix  3      [ ]         STREAM     CONNECTED     9735     1262/dockerd         
unix  2      [ ACC ]     STREAM     LISTENING     8762     1262/dockerd         /var/run/docker/metrics.sock
unix  2      [ ACC ]     STREAM     LISTENING     5639     1/init               /run/docker.sock
unix  2      [ ACC ]     STREAM     LISTENING     9069     1262/dockerd         /var/run/docker/libnetwork/12421aacefe7.sock

chatgpt did make me create these files aswell
"default"

server {
    listen 80;
    server_name familjenisback.duckdns.org;

    # Allow Certbot to access the challenge directory
    location /.well-known/acme-challenge/ {
        root /var/www/html;  # Ensure this path exists
        try_files $uri =404; # This ensures a proper response for missing files
    }

    # Redirect all other traffic to the Immich application
    location / {
        proxy_pass http://192.168.1.55:2283;  # Direct to Immich app
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

server {
    listen 443 ssl;
    server_name familjenisback.duckdns.org;

    ssl_certificate /etc/letsencrypt/live/familjenisback.duckdns.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/familjenisback.duckdns.org/privkey.pem;

    # Immich application
    location / {
        proxy_pass http://192.168.1.55:2283;  # Direct to Immich app
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}


"family..."

server {
    listen 80;
    server_name familjenisback.duckdns.org;

    # Redirect all HTTP requests to HTTPS
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    server_name familjenisback.duckdns.org;

    ssl_certificate /etc/letsencrypt/live/familjenisback.duckdns.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/familjenisback.duckdns.org/privkey.pem;

    location / {
        proxy_pass http://192.168.1.55:2283;  # Adjust this based on your setup
    }
}

"immich"

server {
    listen 80;
    server_name familjenisback.duckdns.org;

    location / {
        proxy_pass http://192.168.1.55:2283/;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

hope this added some more info, what is a nat evice? I did do something that used iptables, you can find it in the pastebin i tihnk