starwhiz / docker_deployment_notes Goto Github PK

Hi.

your initial unbuntu setup script needs an addition for the ssh setup

Unbuntu have now added a permission under /etc/ssh/sshd_config.d/50-cloud-init.conf as PasswordAuthentication yes
It overides the /etc/ssh/sshd_config setting.

If you add in
sudo sed --in-place 's/PasswordAuthentication yes/PasswordAuthentication no/' /etc/ssh/sshd_config.d/50-cloud-init.conf

It fixes it.

When I initially start the docker container and setup my account, the apps install and then I go into a loading state for about 60 seconds before I get a 504 Gateway Time-out.

Also, would it be possible to get a guide on PiHole? I tried to do it myself, but I got errors about the ports already being bound, and I couldn't figure out how to get around it.

I just tried to use the seafile notes to get my seafile server up and running in docker + caddy setup and noticed that there is a small change that has to be done to the gunicorn.conf file before the server started working (got connection refused error). The thread is here https://forum.seafile.com/t/seafile-and-seahub-start-but-nothing-will-connect-after-upgrade/9204/4 and the change is to modify the default bind = "127.0.0.1:8000 to bind = "0.0.0.0:8000. At least this did the trick for me.

After I edit Caddyfile and use:
docker exec -w /etc/caddy caddy caddy reload

result is:

{"level":"info","ts":1708475357.2048461,"msg":"using adjacent Caddyfile"}
{"level":"warn","ts":1708475357.205982,"msg":"Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies","adapter":"caddyfile","file":"Caddyfile","line":2}

My Caddyfile:

portainer.{$MY_DOMAIN} {
  reverse_proxy portainer:9443 {
    transport http {
      tls
      tls_insecure_skip_verify
    }
  }
}

mumble.{$MY_DOMAIN} {
        reverse_proxy mumble-server:64738
}