How to setup this product without acme and only with http protocol?

Hi! Self hosted proxy server by Apache. All TLS certs distributed by this proxy. So I need to know how I can avoid these little bit crazy appctl setup procedure. My proxy server running in docker with network in external mode. How I can set static network address for nginx-proxy misago host for the feature redirection via my own proxy (via http)? And how I can revoke TLS from Lets Encrypt if container volumes already was deleted?)

nginx-lets-encrypt-1  | Creating/renewal mydomain.com certificates... (mydomain.com www.mydomain.com)
nginx-lets-encrypt-1  | [Wed Mar  5 15:24:38 UTC 2025] Using CA: https://acme-v02.api.letsencrypt.org/directory
nginx-lets-encrypt-1  | [Wed Mar  5 15:24:38 UTC 2025] Creating domain key
nginx-lets-encrypt-1  | [Wed Mar  5 15:24:38 UTC 2025] The domain key is here: /etc/acme.sh/pro@mail.com/mydomain.com/mydomain.com.key
nginx-lets-encrypt-1  | [Wed Mar  5 15:24:38 UTC 2025] Multi domain='DNS:mydomain.com,DNS:www.mydomain.com'
nginx-lets-encrypt-1  | [Wed Mar  5 15:24:38 UTC 2025] Getting domain auth token for each domain
nginx-lets-encrypt-1  | [Wed Mar  5 15:24:41 UTC 2025] Getting webroot for domain='mydomain.com'
nginx-lets-encrypt-1  | [Wed Mar  5 15:24:41 UTC 2025] Getting webroot for domain='www.mydomain.com'
nginx-lets-encrypt-1  | [Wed Mar  5 15:24:42 UTC 2025] Verifying: mydomain.com
nginx-lets-encrypt-1  | [Wed Mar  5 15:24:45 UTC 2025] mydomain.com:Verify error:84.244.31.122: Fetching http://mydomain.com/.well-known/acme-challenge/YFV4saG4boIN6G0Tep662SifupVjjchnWYI6DErZR5I: Connection refused
nginx-lets-encrypt-1  | [Wed Mar  5 15:24:45 UTC 2025] Please check log file for more details: /dev/null
nginx-lets-encrypt-1  | Sleep for 3600s
nginx-lets-encrypt-1  | 2025/03/05 15:30:02 Received event start for container e6092190a474
nginx-lets-encrypt-1  | 2025/03/05 15:30:03 Received event die for container e6092190a474
nginx-lets-encrypt-1  | 2025/03/05 15:30:08 Debounce minTimer fired
nginx-lets-encrypt-1  | 2025/03/05 15:30:08 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'
nginx-lets-encrypt-1  | 2025/03/05 15:30:31 Received event start for container 22f4512cd639
nginx-lets-encrypt-1  | 2025/03/05 15:30:32 Received event die for container 22f4512cd639
nginx-lets-encrypt-1  | 2025/03/05 15:30:37 Debounce minTimer fired
nginx-lets-encrypt-1  | 2025/03/05 15:30:37 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'

Trying to deploy clear. Got an error. Seems a trouble with nginx-lets-encrypt container. Not sure what is it.
p.s. hostname is changed in this code block for anonymously. Server taken real.

Yes it is. mydomain.com - example. Server with real hostname

misago_docker-nginx-proxy-1          misago_docker-nginx-proxy                    "/app/docker-entrypo…"   nginx-proxy          3 hours ago   Up 19 minutes   0.0.0.0:443->443/tcp, [::]:443->443/tcp, 0.0.0.0:8083->80/tcp, [::]:8083->80/tcp

Default port was changed..
p.s. but TLS verification requests to default :\ seems certbot unknown about custom port?

The thread Install misago in a podman pod under linux shows how to split the services out and install separately, for custom requirements.

It includes a section on how to apply a custom configuration to the nginx component. You would have to research how to configure that for localhost (which I believe is possible).

You can use a similar procedure for docker, as for the podman example. Just don't put the containers in pods.

YEEEEEP!!!! BROS!! I DO IT. IT WORKS!!! Thanks a lot for your job. I really like! Thanks. I forgot open additional custom TCP port and ./appctl setup incorrectly finished. Now all works. Via my own proxy. Thx.