HanSolo97

Ui ok, das sieht aufwändig aus, schau ich mir aber gerne an sobald ich Zeit hab, und versuche dann ne kleine Doku für SimpleX daraus zu machen.

Das Problem ist ja dass das SMP Protokoll auf 5223 anfragt. Da kommen wir mit 443 glaube ich nicht weit, oder? smp://myserver:443 funktioniert bestimmt nicht, oder?

Hi @wubl. Die Unraid-Templates für Simplex habe ich erstellt, Fragen beantworte ich gerne soweit möglich. Schau mal hier, die Lösung heißt, Docker Network + Nginx Proxy Manager mit TCP Stream. https://codeberg.org/HanSolo97/unraid-templates/issues/7#issuecomment-2040207 Richtige Anleitung kommt aber noch auf Coderberg, bin nur noch nicht dazu gekommen.

I just discovered the label "net.unraid.docker.managed=dockerman" by looking at a existing container, that i pulled from community applications. Also as far as i know, templates are located in /boot/config/plugins/dockerMan/templates-user/ and are named "my-<container-name>.xml" So i tried setting this label, and also creating an xml file with the correct name. But it still doesnt connect to the template. Not that easy But slowly getting more and more knowledge about how this actually works in the background

Needed to change it to work, removed the deploy section and just set: labels: - "net.unraid.docker.icon=...." Now icons being pulled, even without restart of unraid Is it also possible to link a Template XML that way?

Added this to my docker-compose.yml: deploy: labels: net.unraid.docker.icon: https://example.org/example.png Is that how you meant it? Doesnt seem to work so far.

Hmm, i guess thats not working for me. I got a Master Container (with template) but this one only spawns 2 other Containers via Docker Compose and then deletes itself. If it was e.g. just connected by the container name, i could include a script to the Master Container, which puts an Template xml to the spawned containers. Thats why i try to understand how the actual running container is connected to the template.

I'd like to understand, how exactly are the Template XMLs connected with the actual running containers. (e.g. for providing the Icon) I want to know it, because i want to link a Template XML (e.g. by script) to an existing container, that has been spawned by docker-compose. Is that possible? I know its not really how CA is meant to be used, but this is a very special use case

Hey @Squid, i got a question regarding my Template Error: The Problem here is, that the Container Port is 80, but this one is used for most users by the reverse Proxy, so i changed the Host Port to 8123. Thats why the WebUI should point to 8123 instead of 80, to have an ip + port that can be adressed by reverse proxy then. Is there a way to make CA ignore this Issue, and not making the automatic correction?