Attempted to deploy, receiving "Server Error" after trying to create account/send password reset email about app

[nguyenkims]

@dohlin Glad that you have been able to debug all this out! The database needs to be reached by both containers and Postfix (which is outside of Docker) so port binding is a must. You could use another port than 5432 if this port happens to be occupied on your VM/server though.

The alias suffix like "cat", "chat" is there to avoid one person taking all "nice" aliases. This protection doesn't make sense in self-hosted SimpleLogin though, #37 adds an option to disable this suffix. Once the PR is merged, please make sure to set the DISABLE_ALIAS_SUFFIX in your config file to disable alias suffix.

[dohlin]

Excellent thank you! One last question - when the PR is merged and the .env file is updated with that option, what is the best way to update the running docker container? Is it to remove the docker container and image and then simple re-pull/re-setup the container? Or is there a better way?

[nguyenkims]

If you can afford some small downtimes, I would do

1. docker pull simplelogin/app to get the latest docker image. This could take a while, depending on your network.
   1b. Update the config file to add DISABLE_ALIAS_SUFFIX option.
2. remove all SimpleLogin containers (you don't need to remove the Postgres container) by docker rm -f sl-migration sl-app sl-email sl-cron
3. start them again using the commands in the README.

SimpleLogin containers are down during step 2 & 3. but no email is lost as Postfix is still running.

Please note that the Docker network has changed from 1.1.1.1 to a better one (240.0.0.0), if you deploy SimpleLogin before that change, you might need to redo the network setup. Sorry about this breaking change!

[dohlin]

Thank you, this all worked great. Got the docker network updated, containers removed/reassigned, & postfix main.cf file updated too. Thanks again!