Zitat von 2TUN2

Special for KM0201

Rate Limits - Let's Encrypt (letsencrypt.org)

Renewals are treated specially: they don’t count against your Certificates per Registered Domain limit, but they are subject to a Duplicate Certificate limit of 5 per week. Note: renewals used to count against your Certificate per Registered Domain limit until March 2019, but they don’t anymore. Exceeding the Duplicate Certificate limit is reported with the error message too many certificates already issued for exact set of domains.

Who lies here?

Alles anzeigen

Telling you, I've done this multiple times a day on my certs (way more than 5) and never had an issue.

But ok, I'll give you the benefit of the doubt. I was constantly adding new/different subdomains so it simply may not have been logging them as duplicates. So we'll say you hit your limit of 5 per day so you had to change your subdomain, because frankly it is irrelevant to this discussion. It still does not change the fact that there is no way you were getting a key before when you said you were.

So was helping someone this morning and he ran into this... (couldn't pull a key due to multiple failed tries)... Didn't realize this, but there is another cert provider in the swag container...

https://docs.linuxserver.io/ge…r-lets-encrypt-vs-zerossl

So if you run into this problem with Lets Encrypt not letting you pull a key due to failed attempts, duplicate attempts, whatever you want to call it (and you're not clearly lying for attention)... I tested it just for grins and it works just the same. The only difference is it offers unlimited certificate attempts. Only thing I found different from the documentation, is the key I pulled with the swag container, does not link to an account on zerossl's website (which is free if you want to try it).... so you can probably skip that. Still provide an email, because I believe you'll get an email when your cert is about to expire.

Simply add this environment variable to the swag portion of the docker-compose file

- CERTPROVIDER=zerossl

and deploy the container again. Other than the unlimited attempts, they run, renew, etc. exactly the same.

Post your yml file. Hide all passwords, emails, and keys. It may be just a typo (or not ).

Zitat von hjzwiers

Here is the yml file:

version: "2"

services:

nextcloud:

image: ghcr.io/linuxserver/nextcloud

container_name: nextcloud

environment:

- PUID=1000 #change PUID if needed

- PGID=100 #change PGID if needed

- TZ=Europe/Amsterdam

volumes:

- /srv/dev-disk-by-label-DockerDisk/docker/appdata/nextcloud/config:/config

- /srv/dev-disk-by-label-DockerDisk/docker/appdata/nextcloud/data:/data

depends_on:

- mariadb

# ports: # uncomment this and the next line if you want to bypass the proxy

# - 450:443

restart: unless-stopped

mariadb:

image: ghcr.io/linuxserver/mariadb

container_name: nextclouddb

environment:

- PUID=1000 #change PUID if needed

- PGID=100 #change PGID if needed

- MYSQL_ROOT_PASSWORD=***************** #change password

- TZ=Europe/Amsterdam

volumes:

- /srv/dev-disk-by-label-DockerDisk/docker/appdata/nextclouddb:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted

restart: unless-stopped

swag:

image: ghcr.io/linuxserver/swag #uncomment this line and comment the previous one if you want to use the new swag container (see link at bottom of the post)

container_name: swag

cap_add:

- NET_ADMIN

environment:

- PUID=1000 #change PUID if needed

- PGID=100 #change PGID if needed

- TZ=Europe/Amsterdam

- URL=**************.net

- SUBDOMAINS=www,

- VALIDATION=http

- CERTPROVIDER=zerossl

- EMAIL=****************.nl

volumes:

- /srv/dev-disk-by-label-DockerDisk/docker/appdata/swag:/config

ports:

- 443:443

- 80:80

restart: unless-stopped

Had the ports at 81:80 and 444:443 before, but no difference. Went over this several times, and before swag change was running well over a year.

Alles anzeigen

First, 80:80, that has to be changed. the OMV webUI runs on 80. So you either need to change the webUI to another port (I think that is under either Network or General Settings)... or Change the port for swag.

That's the first thing you need to address.

Port settings are right at the top of the OMV menu bar under General Settings, but why didn't you leave it the way it was before; as 81:80 and 444:443?

Indentation of the yml file matters. You may have a small indentation problem but we cannot see it. Your copy/paste into the post left it flat so it's not possible to see that indentation. Place your yml file in a code block from the menu bar above, as:

---
version: "2.1"
services:
  swag:
    image: ghcr.io/linuxserver/swag
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=100
      - TZ=America/Chicago
    ...

I'm assuming you're using subdomain or subfolder?

How's your domain setup? Have you checked your CNAME and A Records?

Zitat von Agricola

At least I get a different response to docker-compose up -d this time around:

Code

root@m4omv5:/home/docker1/nextcloud# docker-compose up -d
Creating network "nextcloud_default" with the default driver
ERROR: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-0b1adf19895e -j DOCKER: iptables v1.8.2 (nf_tables):  RULE_INSERT failed (Invalid argument): rule in chain FORWARD
 (exit status 4)

all I did was run apt-get reinstall docker-compose and then the up -d command above. What have I done now?

Hmm, weird.

If it were me, before I tried reinstalling... I'd uninstall docker with the webUI... Maybe even run apt-autoremove (make sure it doesn't want to uninstall openmediavault before accepting) to remove any dangling packages from docker. apt autoclean to clean anything up... then use the webUI to reinstall docker.

As long as your containers are not stored at /var/lib, and you point at your containers in the docker settings after reinstall... there's shouldn't be any real risk of data and configuration loss for your containers.

KM0201 where did you get that (old) post? I haven’t had Nextcloud on my NanoPi M4 in maybe a year or more. It’s just a backup server now. At the time Docker would not work with the M4 and the new ip tables. Once I was able to revert to the older legacy ip tables Nextcloud installed fine. This was before ryecoaaron put an ip tables switch in (I think) OMV-extras, so I had to search the web for a command line solution.

Zitat von Agricola

KM0201 where did you get that (old) post? I haven’t had Nextcloud on my NanoPi M4 in maybe a year or more. It’s just a backup server now. At the time Docker would not work with the M4 and the new ip tables. Once I was able to revert to the older legacy ip tables Nextcloud installed fine. This was before ryecoaaron put an ip tables switch in (I think) OMV-extras, so I had to search the web for a command line solution.

That's a really good freaking question..lol. I swear I had an alert pop up on it and clicked it and read the post... I didn't even look at the date, and now I see I don't have an alert on it (that was how I found it)..

Forum gremlins at work.

KM0201 That was post #38 of this thread; October 7th, 2019!