Yes, but this adress is going to the swag screen
Posts by harold.mouras
-
-
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
-
Code
Display Moreservices: 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 :
Code
Display More--- 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 :
Code
Display Moreserver { 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
-
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
Hello,
yes, as 0 with the PUID, that works. Should I let the 0 now or change something else ?
Thank you again,
Harold
-
Hello,
thank you so much. This does not work.
The logs are :
-----
Variables set:
PUID=1001
PGID=100
TZ=Europe/Paris
URL=hmouras.duckdns.org
SUBDOMAINS=wildcard
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=duckdns
CERTPROVIDER=
DNSPLUGIN=
EMAIL=hmouras@gmail.com
STAGING=Created .donoteditthisfile.conf
the resulting certificate will only cover the subdomains due to a limitation of duckdns, so it is advised to set the root location to use http://www.subdomain.duckdns.org
Different validation parameters entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created
Saving debug log to /var/log/letsencrypt/letsencrypt.log
No certificate found with name hmouras.duckdns.org (expected /etc/letsencrypt/renewal/hmouras.duckdns.org.conf).
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
Using Let's Encrypt as the cert provider
SUBDOMAINS entered, processing
Wildcard cert for hmouras.duckdns.org will be requested
E-mail address entered: hmouras@gmail.com
dns validation via duckdns plugin is selected
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Account registered.
Requesting a certificate for *.hmouras.duckdns.org
Waiting 30 seconds for DNS changes to propagateCertbot failed to authenticate some domains (authenticator: dns-duckdns). The Certificate Authority reported these problems: Domain: hmouras.duckdns.org Type: unauthorized Detail: Incorrect TXT record "" found at _acme-challenge.hmouras.duckdns.org
Hint: The Certificate Authority failed to verify the DNS TXT records created by --dns-duckdns. Ensure the above domains are hosted by this DNS provider, or try increasing --dns-duckdns-propagation-seconds (currently 30 seconds).
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
ERROR: Cert does not exist! Please see the validation error above. Make sure you entered correct credentials into the /config/dns-conf/duckdns.ini file.END OF LINE
Helpful ?
-
Thank you for your message.
On the router, the 443 port is going to 443 with the IP adress of the OMV system.
I did not check the logs, how to get them ?
yes, I think the local path is correct
-
Well, I am sorry but my swag worked since almost two years but was broken some days ago.
Even if I succeded in seting up it years ago, I have to say that I do not remember abotu these settings, so I am begining again from zero.
What I did :
- in the router I did forward port 443 to port 443 specifying the local IP of the OMV system;
- in portainer, I took your stack and deplyed it, but this does not work.
Here is the yml of the stack :
Code
Display Moreservices: swag: image: lscr.io/linuxserver/swag:latest container_name: swag hostname: swag cap_add: - NET_ADMIN environment: - PUID=1000 - PGID=1000 - TZ=Europe/Paris - URL=myduckdns - VALIDATION=duckdns - SUBDOMAINS=wildcard - DUCKDNSTOKEN=mytoken volumes: - /etc/localtime:/etc/localtime:ro - /srv/dev-disk-by-uuid-92231eb7-e8d7-49e4-8445-0aaa5c450b26/config/swag:/config ports: - 443:443 #- 82:80 restart: unless-stopped
-
Hello again,
I changed my swag YML to :
---
version: "2.1"
services:
swag:
image: lscr.io/linuxserver/swag:latest
container_name: swag
cap_add:
- NET_ADMIN
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Paris
- URL=
- VALIDATION=duckdns
- SUBDOMAINS=wildcard
- CERTPROVIDER= #optional
- DUCKDNSTOKEN=
- EMAIL=
volumes:
- /srv/dev-disk-by-uuid-92231eb7-e8d7-49e4-8445-0aaa5c450b26/config/swag:/config
ports:
- 444:443
#- 82:80
restart: unless-stopped
On the router, I directed the port 443 to 444.
Am I on the right way ?
Thanks
-
Thank you.
The YML is :
---
version: "2.1"
services:
swag:
image: lscr.io/linuxserver/swag:latest
container_name: swag
cap_add:
- NET_ADMIN
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Paris
- URL=mysubdomain.duckdns.org
- VALIDATION=duckdns
- SUBDOMAINS=wildcard
- CERTPROVIDER= #optional
- DUCKDNSTOKEN=mytoken
- EMAIL= mymail
volumes:
- /srv/dev-disk-by-uuid-92231eb7-e8d7-49e4-8445-0aaa5c450b26/config/swag:/config
ports:
- 443:443
#- 82:80
restart: unless-stopped
and LAN IP is 192.168.0.21
This is what you needed ?
Thank you so much,
Harold
-
Well, did I do well : I forwarded my 443 port to the 443 port specifying the LAN IP.
-
Hello, thank you for your mail. The Ip adress of my box did not change, only the local adress of the OMV system. In DuckDNS, you just specify the IP of the box, right ?
-
Dear all,
I have an OMV system which worked very well with swag and a duckdns subdomaine to access it from the internet.
This worked very good. Recently, only the IP adress of the OMV system changed. I made the change in all the *.subdomain.conf files replacing the old IP adress by the new one but this does not work. Also, as I did one time, I did open on my router the 443 port, but this does not work as well.
Any help on that would be very nice.
Thank you very much,
Harold
PS: eveything is working well locally on the network.
-
Hello,
I have an OMV6 system. I did activate FileBrowser under OMV services but when clicking on "Open Interface", nothing appears...
Any idea ?
Thank you,
Best regards,
Harold
-
To add the samba folder in Nextcloud go to the External Storage tab in the administration settings. There you must open the "External storage" drop-down menu and choose SMB/CIFS. After that you must complete the fields on the right with the appropriate parameters, it will ask you for a username and password with permissions to access that folder and the IP of the OMV server among other things.
Thank you very much for your help.
I am trying to follow this.
In the field "Hôte" I understood that I put the IP of the host.
What should I put in the "Partage" field ?
Thank you very much in advance,
Best regards,
Harold
-
Dear all,
I have an OMV6 system with photoprism. Everything is working well but I am unable to share picture through the shared link crated by photoprism. DO you have any idea ?
Thanks,
Harold
-
Hello,
here is my file :
---
version: "3"
services:
portainer:
image: portainer/portainer-ce:latest
container_name: portainer
restart: unless-stopped
security_opt:
- no-new-privileges:true
volumes:
- /etc/localtime:/etc/localtime:ro
- /var/run/docker.sock:/var/run/docker.sock:ro
- portainer-data:/data
ports:
- 9000:9000
volumes:
portainer-data:
external: true
name: portainer_data
Thank you,
Harold
-
Thank you.
I did create the data folder.
When I try now to UP portainer I have :
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-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/portainer/portainer.yml' --env-file '/srv/dev-disk-by-uuid-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/portainer/portainer.env' --env-file '/srv/dev-disk-by-uuid-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/global.env' up -d 2>&1': external volume "portainer_data" not found
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-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/portainer/portainer.yml' --env-file '/srv/dev-disk-by-uuid-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/portainer/portainer.env' --env-file '/srv/dev-disk-by-uuid-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/global.env' up -d 2>&1': external volume "portainer_data" not found in /usr/share/openmediavault/engined/rpc/compose.inc:693
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(622): OMVRpcServiceCompose->{closure}()
#1 /usr/share/openmediavault/engined/rpc/compose.inc(668): OMV\Rpc\ServiceAbstract->execBgProc()
#2 [internal function]: OMVRpcServiceCompose->doCommand()
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(122): call_user_func_array()
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()
#5 /usr/sbin/omv-engined(535): OMV\Rpc\Rpc::call()
#6 {main}
-
Hello,
I just reinstalled a new OMV7 system.
I installed through the shell omv-extras.
I installed the compose pluging.
Then, I go to Compose->Files-> Add from example.
I choose portainer, which appears as "down".
When clicking "Up", I get the following error message :
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-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/portainer/portainer.yml' --env-file '/srv/dev-disk-by-uuid-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/portainer/portainer.env' --env-file '/srv/dev-disk-by-uuid-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/global.env' up -d 2>&1': service "portainer" refers to undefined volume CHANGE_TO_COMPOSE_DATA_PATH/portainer/data: invalid compose project
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-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/portainer/portainer.yml' --env-file '/srv/dev-disk-by-uuid-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/portainer/portainer.env' --env-file '/srv/dev-disk-by-uuid-54e4c1a4-2515-4fdf-a714-e060e7726ce5/compose/global.env' up -d 2>&1': service "portainer" refers to undefined volume CHANGE_TO_COMPOSE_DATA_PATH/portainer/data: invalid compose project in /usr/share/openmediavault/engined/rpc/compose.inc:693
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(622): OMVRpcServiceCompose->{closure}()
#1 /usr/share/openmediavault/engined/rpc/compose.inc(668): OMV\Rpc\ServiceAbstract->execBgProc()
#2 [internal function]: OMVRpcServiceCompose->doCommand()
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(122): call_user_func_array()
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()
#5 /usr/sbin/omv-engined(535): OMV\Rpc\Rpc::call()
#6 {main}
What did I do badly ?
Thanks,
Harold