Swag is not working anymore

Thanks raulfg3

On my test setup I haven’t got any port redirects on my router at all. Container should still start ok.

I do think the OP is very close now though.

You are in business. Good news.

I would not recommend that you run the container as root (PUID 0). This is easy to fix and will apply to other containers if/when you use them.

The problem is permissions/ownership of the folders/files that the container creates when it first runs. You just need to change the permissions recursively on your local swag config folder ( /srv/dev-disk-by-uuid-92231eb7-e8d7-49e4-8445-0aaa5c450b26/config/swag)

You can do this using winSCP (if you use windows) or from the cli (i.e. terminal via ssh). I would recommend you download and use winscp as it is a useful tool/application.

From the cli you will need to run (as root so using sudo) - see below.

Then update your stack and redeploy.

Good luck.

sudo chown -R 1000:100 /srv/dev-disk-by-uuid-92231eb7-e8d7-49e4-8445-0aaa5c450b26/config/swag

All good.

Did you change folder owner to 1000 and the container is working?

With your setup you need to port forward 443 to 443 on ip 192.168.0.12

Also in your reverse proxy config I think there is a mistake. Try:

set $upstream_proto http;

No worries.

If you have more than one swag docker on your network you will need to use a different port for swag and forward this to the other system

Also check/try the change

set $upstream_proto http;

I see now I am looking at your post on a computer (not on my iphone).

Setup looks ok I think but you need to use https not http for url.

https://heim.anotherdomain.duckdns.org

That indicates there is something wrong with your reverse proxy config file for heim. I don't use heim so I do not know to set it up.

Have you tested access from outside your network or are you doing your testing on the lan?

Do you have adguard or pihole on your network with any DNS re-write rules?

A couple of things that might help but not sure.

1. in your swag yaml I think you need to change your port mapping to 444:443 as the container is listening on 443 (not 444).

    ports:
      - 444:443

2. This is very minor and will not be the issue but in your heimall yaml you have 1000 as PGID and PUID. This is unusal.

You have also made some errors with your heimdall yaml. It would help if you read the docker docs.

You can't just change the container port inside your yaml as the container is 'built' using this port. so you need something like this - note I have only changed the host port and this is mapped to the container port that is not changed.

    ports:
      - 81:80
      - 458:443

Then you need to continue with this logic into your reverse proxy config - see below. Note that I am using the https port/config.

so the connection url is https://heim.xxxx

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name heim.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
   
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app 192.168.0.12;
        set $upstream_port 458;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }
}