wastl0815
wastl0815
hi there, thx for the fast reply. i tried invoke update on the server container (container still running). And after invoke update restarted the server container. Unfortunately no changes See...
sorry for the huge font....dont know why is is converted that way
you need the compose and the env files as well?
yes, this the whole log file when using invoke update on the server container I used invoke static instead: log-file below /home/inventree # invoke static Python version 3.11.8 - /usr/local/bin/python3...
yes, i had to change the original compose file from the inventree website because when using the original file error messages occur on portainer/stack. I wasn't able to get it...
ah you are right....thank you i added the proxy to the compose file but unfortunately the proxy container crashes with some connectivity errors: ``` failed to deploy a stack: Network...
Thank you. You are right Port 443 was blocked by a hidden service. I had to change to port 81 because port 80 was als blocked by another application @matmair...
If the Caddyfile is stored in the "Caddyfile" folder and is in the same folder as the compose file and the env file and i use this command volumes: -...
@SchrodingersGat Thanks a lot for your reply I swipped all files, images, containers, volumes etc.... and created a clean new stack. This time the stack was composed without any error...