Erreur letsencrypt après mise a jour nextcloud du store officiel vers dernière version disponible
Hello, I tried to update the version of nextcloud that is on the official store, I have a problem in the installation logs but I can't find where it can come from? It looks like he is trying to register the domain suggested to the installation interface instead of the one entered!! See screenshot for error message.
If anyone has an idea of where it can come from
20 Replies
The docker-compose.json file is identical to that of the official store I just modified the docker image to the latest version
I just modified the docker image to the latest versionhow did you do that also what do you specified as domain name - and how do you call the app? "choose open method"
I modified this line in the docker-compose.json file
please do not edit the app - files. to customize any app follow :
https://runtipi.io/docs/guides/customize-app-config
Customize app config
Homeserver management made easy
I did not modify it on the official store I recovered the docker-compose.json that I modified and tested on my store in test
Create your own app store
Homeserver management made easy
Yes
do you have a link to that repo to have a look?
Sent in private message because I'm starting in all this and want to be sure that everything works before sharing publicly
Very complicated for me because I had never touched development before last month. But by doing so, we learn😉
looks good - you do not need the docker-compose.yml btw - this gets created dynamically from the docker-compose.json
what do you have configured for the settings in the tipi gui for that app ?
We will really say that letsencrypt wants to register the domain name that is suggested and not the one entered it's strange
what do you have configured for the settings in the tipi gui for that app ?
Sent in private 👍
GitHub
routers have hard coded names that wont work with the new appstore ...
runtipi-appstore/apps/nextcloud/docker-compose.json Line 37 in f86e0ad "traefik.http.routers.nextcloud.middlewares": "nextcloud,nextcloud_redirect,nextcloud-https", runtipi-apps...
tested the corrected version on the official store version and the problem is the same with additional logs
mmh. yeah the pr is not correct, i am pretty sure
for comparison an example i use https://github.com/falkheiland/runtipi-appstore/blob/24c2848daff90872af15d0929bb6eac883ad6141/apps/freshrss-oidc/docker-compose.json#L39
GitHub
runtipi-appstore/apps/freshrss-oidc/docker-compose.json at 24c2848d...
Custom Tipi App Store. Contribute to falkheiland/runtipi-appstore development by creating an account on GitHub.
i made a comment in the original issue - for the time being, i suggest try using the nextcloud-mini or my nextcloud-fpm as a template / copy
After :
19T00:46:27Z ERR Unable to obtain ACME certificate for domains error="unable to generate a certificate for the domains [nextcloud-nextcloud-migrated]: acme: error: 400 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Invalid identifiers requested :: Cannot issue for "nextcloud-nextcloud-migrated": Domain name needs at least one dot" ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory domains=["nextcloud-nextcloud-migrated"] providerName=myresolver.acme routerName=websecure-nextcloud@docker rule=Host(
nextcloud-nextcloud-migrated)