Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some steps of video not described in README #9

Open
bayareacoder opened this issue Jun 8, 2020 · 1 comment
Open

Some steps of video not described in README #9

bayareacoder opened this issue Jun 8, 2020 · 1 comment

Comments

@bayareacoder
Copy link

HI,
excellent work to simplify the deploy of RC on DO.
I have this working BUT it requires the extra steps in your video:

  • apt update / apt upgrade
  • reboot
  • make start
  • optional: check w LazyDocker all services are up.

Also, the DNS (CAA and A records) need to be configured BEFORE you run the Ansible program as otherwise the certificate creation will fail.

I would suggest to add the above to the written tutorial.

@ghost
Copy link

ghost commented Jul 31, 2020

Also, the DNS (CAA and A records) need to be configured BEFORE you run the Ansible program as otherwise the certificate creation will fail.

The way Traefik works if it's not able to get a cert (which it won't if the CAA record isn't in place at the time the playbook is run) it will eventually timeout with too many attempts and tell you so in the docker logs (use lazydocker to view traefik logs). At this point you can still add the CAA record to DO and then bring down the traefik service for a bit so the timeout refusal period has passed then bring traefik back up and it'll try again. This is the same way it worked with Traefik v1. When the traefik service comes back up it'll attempt to get that cert again an when it does docker logs for traefik will no longer show too many attempts when attempting to get the LE wildcard cert. At which point SSL will be functional.

Also, since it's not covered in the docs anywhere here's the CAA record I used which worked well for me and I added only after running the ansible playbook the first time around:

Screen Capture_select-area_20200731123014

Also, for the sake of edification, anyone using Route 53 as your domain registrar please note there are not one but two places which you may adjust nameservers: (1) the NS record and (2) the registered domain. To point to DO you need to adjust (2) for proper DNS delegation. It takes about 30 minutes or so and AWS will send an email when it's finished. Note however Route 53 supports CAA records so you may choose not to delegate though you may find it easier if you do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant