Posts by harold.mouras

Dear Community,

I have an OMV system with nextcloud installed. I can access to nextcloud to a browser throuth the URL https://nextcloud.mydomain.duckdns.org, but when I do enter this adress in the Nextcloud sync client, I have this error message :

« The polling URL does not start with HTTPS despite the login URL started with HTTPS…. »

Any idea about my mistake ?

Thank you,

Harold

Well, this is crazy but I was able to redeploy swag under port 443, and now everything is working meaning https://www.mydomain.duckdns.org inside and outside of my network, also https://emby.mydomain.duckdns.org.

I just forward 443 to 443 on my router for the IP address of the NAS.

Thank you for your help, everything is working now.

Harold

Also, assuming that I keep this possibility with the address https://mydomain.duckdns.org:447, how am I able to reach for example emby through http://emby.mydomain.duckdns.org...meaning all the set up subdomain mentioned in the proxy-confs subfolder of swag ?

Quote from jata1

You have been having a lot of fun getting this working.

I think this issue you have now is that when you are on your lan (e.g. at home with client connected to your wifi or wired) then https://mydomain.duckdns.org will not resolve. You need https://mydomain.duckdns.org:447

When not on your home network (e.g. on mobile network) then https://mydomain.duckdns.org will work but https://mydomain.duckdns.org:447 will not work.

Can you test this - then I know the issue and can help you fix it

FYI port forward rules on the router only apply to connections to your wan (not lan)

Display More

I am sorry. I made a bast verifications. When I am either on my home network or mobile network, the same address (https://mydomain.duckdns.org:447) but not https://mydomain.duckdns.org

Quote from jata1

Out of interest, what service (omv, containers, other) is using the standard https port 443?

My first choice strategy to fix this issue would be to free up port 443 and then run swag 443:443 - but this is not always possible/easy.

The reason is that then you can use swag easily for everything - including whatever is currently using port

Hello,

I did not find any containers using port 443 in the list.

I attach the list, maybe you will be better than me

Best regards,

Harold

Waouh

Exactly…

Hello,

I was able to deploy swag on port 447 with such a stack. :

services:
  swag:
    image: lscr.io/linuxserver/swag
    container_name: swag
    hostname: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Paris
      - EMAIL=mymail
      - URL=mydomain.duckdns.org
      - SUBDOMAINS=wildcard
      - VALIDATION=duckdns
      - DUCKDNSTOKEN=mytoken
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /srv/dev-disk-by-uuid-a4573920-1223-409f-95b0-eb4903d28617/appdata/swag:/config
    ports:
      - 447:443
    restart: unless-stopped

I forwarded the port as follows on my router like shown on the attached pic. OMV is working on the port 88.

With such settings, going to https://mydomain.duckdns.org goes nowhere, http://... also....

What did I wrong....

Thank you for your mail. If I understand well, I changed my YML as follows:

 ports:
      - 445:443
    restart: unless-stopped

When I try to redeploy the stack , I get :

failed to deploy a stack: Container swag Creating Container swag Created Container swag Starting Error response from daemon: driver failed programming external connectivity on endpoint swag (7427634feb47015984e16e0bbebf5ed9d3e5b508d23a1eb6292d4ccae0cf9080): failed to bind port 0.0.0.0:445/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:445: bind: address already in use

Meaning that port 445 is also in use ?

Dear all,

I don't understand what is happening. On the same system, I am trying to redeploy swag after a change of IP address, but as a first problem, I cannot recreate a working container form the stack I had working before.

I have this error message :

failed to deploy a stack: Container swag Creating Container swag Created Container swag Starting Error response from daemon: driver failed programming external connectivity on endpoint swag (6031375398d271be83813bc09250e6b078f3a6538e9e07b77448fab6a78d9490): failed to bind port 0.0.0.0:443/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use

Do you have any idea about the problem ?

Thank you very much in advance,
Harold

Well, I tried to install NPM by deploying a stack from your YML, but I have now two docker containers runing as shown on the attachement.

I cannot access to the GUI by typing http://NAS-IP:81

Well, I do not understand anything.

http://jellyfin.mydomain.duckdns.org goes to OMV7 login page

https://jellyfin.mydomain.duckdns.org does not work.

Hello,

thank you for your message.

Quote from raulfg3

1 - EMAIL is not well indented

2 - PGID probably need to be 100 instead of 1000

Ok, I did these changes.

Quote

3 - you need to edit files on Nginx path to teach swag to resolve names , including "mydomain" name

4 - SWAG is used to resolve names like https://omv.mydomain.duckdns.org or https://plex.mydomain.duckdns.org but as I say in point nº 3, you need to edit several files on swag path

I know that I have to edit the files in the proxy-confs subfolder. Lets have an example. For example, I have now jellyfin runing as a container on the system It is reachable by typing locally NAS-IP:8096. I edited the file jellyfin.subdoamine.conf as follows :

server_name jellyfin.*;

    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.32;
        set $upstream_port 8096;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_set_header Range $http_range;
        proxy_set_header If-Range $http_if_range;
    }

    location ~ (/jellyfin)?/socket {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app jellyfin;
        set $upstream_port 8096;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }

    # Restrict access to /metrics
    # https://jellyfin.org/docs/general/networking/monitoring/#prometheus-metrics
    location /metrics {
        allow 192.168.0.0/16;
        allow 10.0.0.0/8;
        allow 172.16.0.0/12;
        allow 127.0.0.0/8;

        deny all;

        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app jellyfin;
        set $upstream_port 8096;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;
    }
}

I do not reach anything when typing http://jellyfin.mydomain.duckdns.org.

Maybe I did not well understood your point :

Quote

3 - you need to edit files on Nginx path to teach swag to resolve names , including "mydomain" name

Is there a location where I should specify mydomain elsewhere than in the swag YML ?

Thanks,

Harold

Dear all,

I am trying to configure swag on a new OMV7 system.

I did :

• install swag from the compose plugin of OMV7 and not from portainer
• edit the swag compose as follows following advices :

services:
  swag:
    image: lscr.io/linuxserver/swag
    container_name: swag
    hostname: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Paris
        - EMAIL=myemail
      - URL=mydomain.duckdns.org
      - SUBDOMAINS=wildcard
      - VALIDATION=duckdns
      - DUCKDNSTOKEN=mytoken
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /appdata/swag:/config
    ports:
      - 444:443
    restart: unless-stopped

• the container swag is listed as « up » in green on the list
• redirect on my router the port 443 to 444

When typing on the internet the address https://mydomain.duckdns.org, I do not get the swag interface screen.

Any idea about the problem?

Thank you very much in advance.

Harold

Hello again,

I have again the same problem. Thie Ip adress of my OMV system changed.

I deployed now swag as you adviced me some weeks ago with the compose included in OMV but this does not work.

I did formard the port 443 to 443 on my router with the UP adress of my OMV system.

What did I do wrong ?

Here is the my swag YML :

---
# https://github.com/linuxserver/docker-swag
services:
  swag:
    image: lscr.io/linuxserver/swag:latest
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Paris
      - EMAIL=hmouras@gmail.com
      - URL=my-domain
      - SUBDOMAINS=wildcard
      - VALIDATION=duckdns
      - DUCKDNSTOKEN=my-token
    volumes:
      - /srv/dev-disk-by-uuid-92231eb7-e8d7-49e4-8445-0aaa5c450b26/config/swag:/config
    ports:
      - 443:443
      - 80:80 #optional
    restart: unless-stopped

The error message is :

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker compose --file '/srv/dev-disk-by-uuid-a4573920-1223-409f-95b0-eb4903d28617/containers/swag/swag.yml' --env-file '/srv/dev-disk-by-uuid-a4573920-1223-409f-95b0-eb4903d28617/containers/swag/swag.env' --env-file '/srv/dev-disk-by-uuid-a4573920-1223-409f-95b0-eb4903d28617/containers/global.env' up -d 2>&1': Container swag Starting

Error response from daemon: driver failed programming external connectivity on endpoint swag (e4d4793bcc276bae2586dc3b49492363fdb7c684800b7325b4e84892bd455193): failed to bind port 0.0.0.0:443/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker compose --file '/srv/dev-disk-by-uuid-a4573920-1223-409f-95b0-eb4903d28617/containers/swag/swag.yml' --env-file '/srv/dev-disk-by-uuid-a4573920-1223-409f-95b0-eb4903d28617/containers/swag/swag.env' --env-file '/srv/dev-disk-by-uuid-a4573920-1223-409f-95b0-eb4903d28617/containers/global.env' up -d 2>&1': Container swag Starting

Error response from daemon: driver failed programming external connectivity on endpoint swag (e4d4793bcc276bae2586dc3b49492363fdb7c684800b7325b4e84892bd455193): failed to bind port 0.0.0.0:443/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use in /usr/share/openmediavault/engined/rpc/compose.inc:693

Stack trace:

#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(620): OMVRpcServiceCompose->{closure}('/tmp/bgstatusbO...', '/tmp/bgoutputqA...')

#1 /usr/share/openmediavault/engined/rpc/compose.inc(696): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))

#2 [internal function]: OMVRpcServiceCompose->doCommand(Array, Array)

#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array)

#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1)

#6 {main}

What is wrong with?

Thanks,

Harold

Yes, but this adress is going to the swag screen

I did change the line to http in the heimdall.subdomaine.conf file. Restarted the swag container.

Also as you see in the swag yml, I specified port 444:444 which also I did opened on the router.

Yes, I did change on the first OMV system with the swag problems. It works now perfectly.

My last message was about another OMV system (another PC).

Thanks

services:
  swag:
    image: lscr.io/linuxserver/swag
    container_name: swag
    hostname: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Paris
        - EMAIL=anothermail
      - URL=anotherdomain.duckdns.org
      - SUBDOMAINS=wildcard
      - VALIDATION=duckdns
      - DUCKDNSTOKEN=mytoken
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /appdata/swag:/config
    ports:
      - 444:444
    restart: unless-stopped

I did forward the port 444 to 444 on the router. I can see the swag screen working.

How I did edit an heimdall stack like this :

---
services:
  heimdall:
    image: lscr.io/linuxserver/heimdall:latest
    container_name: heimdall
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - /srv/dev-disk-by-uuid-a4573920-1223-409f-95b0-eb4903d28617/appdata/heimdall/config:/config
    ports:
      - 81:80
      - 458:458
    restart: unless-stopped

set up the heimdall.subdomain.conf under the proxy_confs subfolder of swag like this :

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

    server_name heim.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

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

I can see the heimdall page at http://NAS-IP:81 but not by typing http://heim.anotherdomain.duckdns.org

I do not know what is not well set up.

Thanks,

Harold

Thank you so much for everything

Quote from jata1

It might be file permissions on the directory/files created by the container.

To see if you can get the container to run at all, edit the compose and use 0 (root) as the PUID.

Then redeploy the container (edit stack and redeploy) and post back the log

If you get it working using root, then we can make it safer after

Display More

Hello,

yes, as 0 with the PUID, that works. Should I let the 0 now or change something else ?

Thank you again,

Harold