be sure this part is correctly configured in your docker image
also take a look at your docker log file for pagekit
[general]
host = “0.0.0.0”
http_port = 81
domain = “cmccoy1.click”
db_path = “/home/user/data/domains.sqlite”
[pdns]
api_ttl = 1
dns_ttl = 86400
tunnel_ttl = 60
socket_path = “/tmp/pdns_tunnel.sock”
caa_records = [
“0 issue “letsencrypt.org””,
]
mx_records = []
ns_records = [
[ “ns1.cmccoy1.click”, “13.58.12.155” ],
]
txt_records = []
soa_record = “ns1.cmccoy1.click awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400”
www_addresses = [
“13.58.12.155”,
]
[pdns.geoip]
default = “13.58.12.155”
[pdns.geoip.continent]
[email]
server = “smtp.gmail.com”
user = “@gmail.com"
password = ""
sender = "******@gmail.com”
reclamation_title = “Reclaim your WebThings Gateway Domain”
reclamation_body = “”“Hello,
Your reclamation token is: {token}
If you did not request to reclaim your gateway domain, you can ignore this email.”""
confirmation_title = “Welcome to your WebThings Gateway”
confirmation_body = “”“Hello,
Welcome to your WebThings Gateway! To confirm your email address, navigate to {link}.
Your gateway can be accessed at https://{domain}.”""
success_page = “”" Email Confirmation Successful!
Thank you for verifying your email.
"""error_page = “”" Email Confirmation Error!
An error happened while verifying your email.
"""I believe this is configured correctly. or atleast configured to how i understood it in the other thread
this is the registration server config, take a look at the pageKite config
GNU nano 4.8 /opt/docker/registration-server/config/pagekite.conf
–isfrontend
–ports=4443
–protos=https
–authdomain=cmccoy1.click
–nullui
wait are you talking about from the gateway? i was running ubuntu 20 and realized pagekite probs wont run on that because of python3 switch. so im spinning up a new vm to test that part out
the gateway shouldn’t be the issue, but if you want to be sure, you could try to run both on docker(gateway and registration server)
so it would appear maybe im still having an issue with my dns. so the gateway wasn’t the issue 
. I just dont really have a clue why the registration server logs are complaining about my domain. i can access the domain {cmccoy1.click} and the subdomain {api.cmccoy1.click} from the internet.
the left windows is a cli from the gateway or the registration server?
left is cli for gateway. the right cli is for the registration server
let’S first fix the e-mail issue:
try as server: smtp.gmail.com:465
then we could try to figure out the missing dns record for the challenge
Thank you. it worked my friend. it still wont send my email through my google account via smtp. i had to fix the sender. THANK YOU SO MUCH FRIEND
you can’t use google as email sender since you can’T specify port you should open an issue : https://github.com/WebThingsIO/registration_server/issues
and ask for an option to specify the port and protocol like specified in this topics:
as far as i get in the source, you have to choose an e-mail provider(smtp server) on port 25
im currently trying 587 to see if that might work. I have to rebuild the gateway every time i request a subdomain because it goes right to the instance rather than trying to make a new subdomain
A warkaround could be to set your own local smtp relay that will resend to google
this could help you : https://kifarunix.com/configure-postfix-to-use-gmail-smtp-on-ubuntu-20-04/
587 wont’ work except if you change the source code
BTW: i have opened an issue for this on github, so maybe it will be fix in futur release
I am under the impression that Google is attempting to deprecate USER/PASS authentication and email clients that use this method will stop working in the future. Viewing Google’s security options, you can re-enable “old/insecure” authentication which I had to do once before after they automatically “secured” that option for me breaking my email clients. Google keeps stating in emails to me that this option will/could be eliminated in the future.
Not sure if this will eventually bite email clients like this application in the ass too… Just a thought.
I think this is probably the fix you need @c_anon. The webthings.io instance of the registration server is actually using “smtp.gmail.com” as an outgoing email server so I don’t think the port is the issue. Google documentation only seems to say to use port 465 “if your client begins with plain text before issuing the STARTTLS command.”
The only other difference I can see is that we’re using a Google Workspace account whereas yours looks like a personal GMail account, but as far as I know they use the same SMTP server. If you can’t enable username/password SMTP authentication on your personal GMail account, another option may be setting an app-specific password.
Hope this helps.