Seems to be an issue with a Ghost 3.0 instance sending subscriber magic link emails to users when signing up on a Ghost instance on a Cloudron sub domain. Ghost assumes the domain it should be sending from should include the sub domain e.g. firstname.lastname@example.org, when the blog is at https://demo.mydomain.com.
The sign up form returns "Please enter a valid email address!" but the logs show the following:
Having Email Masquerading enabled for mydomain.com doesn't make any difference. Sending a test email from the Ghost UI works fine as the email comes from email@example.com and I'm guessing doesn't encounter the authentication error.
The Ghost UI doesn't offer the ability to alter the domain part of the sending email address. Is this something that can be modified within the Ghost package for updating / new installations? Also what would be the best temporary solution?
I am able to reproduce the above. It seems that the
demo.mydomain.compart is hardcoded at https://github.com/TryGhost/Ghost-Admin/blob/18605d9d05d09d8f0ca6e918cd49b9703ed050c4/app/templates/components/gh-members-lab-setting.hbs#L184 which is in turn computed from the location where ghost is installed https://github.com/TryGhost/Ghost-Admin/blob/a5c69cc86d5cfefa702400fc7b03454f37f6d2d5/app/services/config.js#L62
I am not sure what the fix is. Do you know why Ghost is not using the mail settings it already has in it's config? (Sending normal member invitations works as expected).
@tkd Sorry. forgot to give the workaround. I have given explanation of the workaround below.
- Add a Domain called
demo.mydomain.comin the Cloudron Domains view. This can have the same DNS settings as
- Now go to Email view and enable masquerading for
- Then change the domain of your existing app installed at
demo.mydomain.comi.e in configure UI -> Location and then in the drop down select
demo.mydomain.comand leave the location field empty. Effectively, the app remains at
demo.mydomain.combut is using the settings of the Cloudron's
On Cloudron, we don't allow apps to send email with arbitrary addresses across domains. So, if an app has to send emails as demo.mydomain.com then it has to be installed under that domain.
Now your invite emails will also go from firstname.lastname@example.org. Hope this is OK. BTW, you can change this "demo.app" in the Email section of the app's configure UI.
- Add a Domain called
@girish Just tested this workaround and it works!
(I set DNS to Manual to save creating another API key and DNS records since the sub-domain is only for development).
There seems to be some typos in the instructions above though between
domain.comthat might be worth fixing to help anyone else searching for a solution on the same too.