Mostly documentation fixes, disable CNAME support by default

What's Changed

• Add UDR to list of supported devices by @Injabie3 in #86
• Add UX to the list of supported devices by @Injabie3 in #89
• Added instructions and variables for Loopia by @adrianrosen in #90
• Update README.md to reflect CNAME changes, update Lego by @kchristensen in #96

New Contributors

• @adrianrosen made their first contribution in #90

Full Changelog: 2.0.3...2.0.4

Route53 credential fix & Custom upstream DNS resolvers

What's Changed

• Fix AWS Timers by @dubhunter in #83
• Add custom upstream DNS resolver by @Injabie3 in #84

New Contributors

• @dubhunter made their first contribution in #83
• @Injabie3 made their first contribution in #84

Full Changelog: 2.0.2...2.0.3

Google Domains support

What's Changed

• Added GoogleDomains to udm-le.env by @slyticoon in #75
• Note: If you're using Google Domains, you'll need at least lego 4.11.0 installed.

New Contributors

• @slyticoon made their first contribution in #75

Full Changelog: 2.0.1...2.0.2

UniFi OS 2.x+ support

This is a continuation of the 2.x pre-release with an additional minor bugfix.

Please create bug reports if you run into issues with Captive Portal or Radius certificates, as those have not really been tested.

Be sure to read the release notes in the release linked above, as there have been some significant changes in the udm-le.env file.

Preliminary UniFi OS 2.x support

Thanks to the hard work of @emlynmac @potto007 and @Lollaskates, we have preliminary support for UniFi OS 2.x.

This is a pre-release and may not totally work for you. Captive portal and Radius support is kind of untested, so please try this out and let us know.

Important Note: There are new fields in udm-le.env so I would suggest you start from scratch and follow the instructions in the readme closely.

If all goes well, I will promote this release to $latest in a week or two.

Known Issues

• Some paths are wrong in the udm-le.env, fixed in https://github.com/kchristensen/udm-le/pull/73/files

Either simplify things, or make it much worse

While adding in support for Radius certificates, I decided to refactor a bunch of the code because it seemed a bit convoluted. When all was said and done, I've renamed or added variables and changed both the on boot script 99-udm-le.sh as well as some variables in udm-le.env.

When upgrading be sure to take note and update your udm-le.env file appropriately as well as replacing the script in /mnt/data/on_boot.d or this won't function as it did before.

I'm marking this as a pre-release for a bit until it gets further testing, but the gist of the changes are that you can now force a service restart even if there isn't a new certificate by setting RESTART_SERVICES=true when invoking the script.

Additionally, I've added support for Radius SSL certificates which can be enabled via ENABLE_RADIUS in the environment file.

Restart fixes for newer firmwares

Minor bugfix release, fixes:

• Fixes restart issues on newer firmwares (v1.11.0-14+)
• Parameterizes Lego docker image versions (be sure to update your udm-le.env file)
• Updates Lego to v4.4.0

Nagging restart issues begone

This release fixes the issue #29 where unifi-os restart fails to properly restart the unifi-os container on boot. Thanks to all that dug into this and figured it out!

It is recommended that everyone upgrade to this release.

Pump up the volume(s)

This release fixes a volume mounting issue where the .secrets directory was not getting mounted into the container at .aws, as well as adding some basic retry logic when running unifi-os restart to try to catch edge cases where the container does not get restarted properly.

Setec Astronomy

This release adds support for both Azure and Google Cloud DNS providers. Be sure to read the (README.md) for implementation details.

Breaking Changes

There are breaking changes in this release! We're moving to a unified .secrets directory moving forward, so regardless of what DNS provider you are using, if it requires that you create additional credentials files they'll need to be moved into .secrets from .aws or .gcloud.

Moving forward this should simplify adding support for additional providers, but if you fail to move your credential files this will stop functioning!

Thanks to all that have contributed!