Hi @billfahle and @evanrobinson,
As @Martin_Verret mentioned, there’s currently a problem issuing free *.webthings.io subdomains due to a change made by our TLS certificate provider.
Please see this previous thread.
The issue is being tracked here and a fix has already landed but it will take a while for it to be packaged up into a new release.
In the meantime you should be able to access the gateway locally and/or use an alternative remote access mechanism.
The way I’d personally do it would be to use my own domain/subdomain and port forward to the gateway, but if you don’t have a static IP address that would require configuring dynamic DNS on your router. If you’d like to use your own domain/subdomain rather than a free *.webthings.io subdomain then there’s information about how to install your own TLS certificates in the README in order to make it secure.
Sorry for any inconvenience.
Ben