47 Replies
reverting to 3.1.0 makes it work again
Hello, thanks for reporting
Can you print out
./runtipi-cli debug
?this is at 3.1.0 again
It seems that on 3.1.1 you don't get the latest docker-compose because we got rid of "tipi-worker" and your error mentions it
Is it possible that you have some custom configs either main docker or traefik altering "tipi-worker"?
i am using the tipi-compose.yml in user-config
Then I guess you'd need to adapt it a little bit
Before updating
we really need a changelog 😉
or rather a description of the change /
Well this update is non-breaking and the release notes says
Merge worker and dashboard in a single runtipi docker image
its breaking for me 😄
We can't support seamless upgrades for custom made configs
can you give me the new docker-compose here, please 🙂 ?
Sure
@Stavros you broke production
No
lol
i am in the process to fix my tipi-compose.yml to a working state. i have to re-add some routers to differentiate between local and exposed ones - so good so far.
what i am missing is the / are the
tls.certresolver: myresolver
entries
those are gone.I'm starting to see a pattern here...
By the way my upgrade to 3.1.1 went fine!
i DID NOT break production
fyi - this is my new tipi-compose.yml with it i can differentiate between local.domain/ip and exposed routers. this way i can get an additional middleware for auth etc working for external access - maybe sth to include ootb later?
why are you readding the labels?
this way i can get an additional middleware for auth etc working for external access
aha
you shouldn't need to change anything in your tipi compose file rather than copying the labels you had on the worker container and dashboard container to the runtipi container nothing else
in a ootb conf maybe . not in my case
why not?
well i kind of did - my previous one was:
in the end i overwrite the standard router rule from
/
to IP + internal domain - and then add an additional one to also have $DOMAIN one toooh ok
@Stavros
what i am missing is the / are the tls.certresolver: myresolver entriesthere is no certresolver label in the new docker-compose.yml - is this intentional?
we didn't touch the labels
they are exactly the same as the old ones just in one container
from the previuos docker-compose.yml:
huh
@Nicolas why did we remove it?
Maybe we missed it?
probably
But I tested both local domain and published
Strange
if you have a valid cert then there is no prob - but you cant renew
Ok then indeed there is a mistake
sorry but i dont see that in the old compose
from 3.1.0
Yes it was here before
(cli)
only in the cli?
Yes
why
Is it the only thing @InfBoumcyCastle ?
Didn't check the runtipi one but it's only for dev those
this is the docker-compose.yml from my latest backup before the update
line 117, 125, 188 are the certresolver
after i changed my tipi-compose to the above version - everythng seems to be ok so far
I'm releasing the missing labels
facing the same problem when upgrading 😄
edited container_name in my tipi-compose, run now fine 🙂
to
and for the PWD bug:
Unknown User•10mo ago
Message Not Public
Sign In & Join Server To View