Somewhere in the past day while trying to solve the PTR problem and getting no help from the Linode tech support system except that my vps setup mx records for the my.domain.com Dashboard and Email looked okay & go look at Cloudron docs (again) I have the problem that I cannot login to https://my.mydomain.com//#/apps or /login.html
You are seeing this page because this domain points to Cloudron server IP but no app is installed on that domain.
Yet my main domain name record in my Linode account https://mydomain.com immediately opens my Mastadon login page as I configured it to do.
So I had a Cloudron application installed on this VPS instance that was used to install both Mastadon and the RoundCube email image.
But the my.mydomain.com dashboard now fails to connect. And https://mymail.mydomain.com/?_task=mail&_mbox=INBOX also doesn't connect and both just give me white pages with --
You are seeing this page because this domain points to Cloudron server IP but no app is installed on that domain.
If I can't get to the Cloudron dashboard I can't look for setting again or signal the application to synch the DNS again from my linode VPS.
I have another domain served by another VPS at Linode and everything works. I can login and see my Cloudron app and my RoundCube app and both run fine. And my Mastadon app works fine. So I've been back and forth comparing both VPS setups and I can't find any critical difference except for domain name.
What, please, is a backdoor to get control of my Cloudron installation? I don't want to waste hours going backwards to set up a brandnew Cloudron just get a new RoundCube and Mastadon setup. The Mastadon account works perfectly.
Thank you for ideas.
How much of https://docs.cloudron.io/troubleshooting/#unreachable-dashboard have you worked through? It does appear you are in the "Unreachable Dashboard" situation presently, though you may have a DNS issue. Knowing the results of the listed troubleshooting steps will help characterize the problem and appropriate solution(s) much better.
@jimcavoli Thank you for your response.
My problem since late last night and today is that I can not login successfully to my RoundCube email.
The username and password connection repeatedly fail.
Using the same username and password I can successfully login to my Cloudron app on my website.
I can even send a test email from Cloudron's dashboard.
I finally thought maybe I should uninstall my RoundCube and I did. Then I installed RainLoop. Same deal. Can not login to the Email application with the Username and password I saved 2 days ago.
I can log in to Cloudron https://my.mydomain.com/login.html with that Username and password.
Both installations of RoundCube and RainLoop said that they would use the existing username and password for the Email app login -- but it does not work. Authentication fails.
I know somewhere in the database the stored validation combination is not matching. Repair does not work.
How can I force the Email configuration set by Cloudron to apply to the Email Admin login?
@debossnow The password will be the same as the password on the Cloudron for login, but the "username" in this case should be the full email address of the mailbox which you'd like to sign into. This is how multiple mail domains can have mailboxes owned by one account. For example, let's say that I have a Cloudron at example.com which handles mail for example.org as well. Let's further say there is a user with the username
adminand a password of
secretpassword. That user could be assigned multiple mailboxes; for the sake of the example, let's say this user
adminis the owner for
firstname.lastname@example.org, and also
email@example.com. In order to sign in to a webmail, such as RoundCube or RainLoop that is attached to the Cloudron mail system, it would be necessary to use the full email address - e.g.
firstname.lastname@example.org- and the same
secretpasswordas the credentials. The Cloudron knows which user (and therefore which password) goes with a mailbox, but of course the webmail client does not and can only provided the intended mailbox.
If there's anything more unusual going on, the Event Log on the email administration page is likely to have some further details.
@jimcavoli Thanks, Jim.
But it does not work that way on my setup.
On an almost duplicate setup with a different domain name the Username to open up the Email application once I click the Cloudron Mail account does NOT require the full domain.
In fact, the name I put into the Username to login does not match either the username or "Full Name".
The Username is De Boss deboss is the account name.
However to login to the Email app as the administrator the working login is "DeBoss" with no space between.
And definitely no email@example.com works with that password.
So now I go back to the other domain with the same setup, but setup a few days later and no combination of the email account login with its domain added "firstname.lastname@example.org" logins. Combo can't be verified.
So, following your advice I set up an entirely new user at this domain while logged in to Cloudron. And gave this user Superadmin privileges. It emailed a confirming invitation which I used to follow the Setup account link.
I set it up and saved and then tried to login.
The new account fails to login to the email application.
Is this Login verified from checking Cloudron servers or from my own database installed with Cloudron and the Email app installation?
When I set up Cloudron the first time it gave me one Username and password. And I continued setting up that domain with a Cloudron installation using that first Username and password.
Now I don't need to use the full domain name to log in to my Email app on that domain, just the username, although it is NOT exactly the same as what my Cloudron User account shows!
Then when I setup my second domain I had to install Cloudron again. It prompted for a new username for that account. I realized everytime I would install Cloudron in other domains that I had to use a new registration each time.
So, even though the installation said FREE if I used the green button it immediately wanted my credit card and a whole new account to be set up for a pay plan.
PLEASE CLEAR THIS UP once and for all.
What you describe does NOT work that way as far as using a full email address in my first domain, as I have described.
The second domain set up days later will not give me access to the email application with two different users following your instructions.
@debossnow you seem to be mentioning and mixing a few different issues, which I am not quite able to understand from your descriptiong.
Just to be clear here, mailboxes have to be created manually and then assigned to a user. After that, one can login using the mailbox address ( email address email@example.com ) and the assigned user's password.
Also regarding the subscription, currently the limitation is one domain (including subdomains of that of course where apps are installed) and 2 apps in the free tier. I think our pricing page does not mention this domain limit, however since only 2 apps are included, many domains make no sense anyways. We will revisit our pricing page details there to clear that up.
Since you seem to be using Roundcube, the login using the full email addresses should work as well as mentioned in https://docs.cloudron.io/apps/roundcube/#multi-domain-setup and I also just verified this on my side.
@nebulon Thank you for answering my query.
It didn't help me, however.
In the actions I just described OBVIOUSLY I could ONLY have made new accounts when I was in the Cloudron dashboard.
Since, after all, I have NO ACCESS to any other controls beyond that.
In the last user account I set up I gave it the greatest Admin privileges and saved it. It did as promised, sent an email from the cloudron server to the outside email account of the new user whose account I had created.
I opened the email and replied to the link which sent me back to the form where I then ADD more elements, such as setting the Password.
Still, once I saved all of this and the new user I created was in the Cloudron list of Users ... my first email account for myself and the email account I just created.
But neither the first email or the second will open up my email app to see its mail accounts dashboard.
For my second instance of installing Cloudron the email app in neither RoundCube or RainLoop opens.
I already successfully went through this process with my first domain and everything works perfectly, So I have gained familiarity that works.
Except your advice fails consistently.
@robi I will try, but what seems obvious at this moment is with Cloudron's authentication server.
When I provisioned another website in my Linode account like the first time I signed up for Linode and decided to try Cloudron so that I could install Mastadon my second Cloudron install using a different email was impaired and I didn't know it.
Obviously this has to do with the Deal between Cloudron and Linode. For weeks now I have been trying to set up 2 domains with 2 instances of Cloudron and Mastadon.
I made all the correct steps to get Cloudron and Mastadon set up in both virtual servers. This whole time I intended to TEST Linode. Whether I should switch my hosted websites over to Linode. I believed the hype about using Cloudron to assist.
I am telling you that NOTHING works for opening up ANY email application in my 2nd Cloudron trial.
The first domain setup works! As advertised.
The second domain setup (same as first) fails consistently.
And in the first domain setup when I click on the mail app logo inside Cloudron it immediately opens up with no login needed.
The second domain setup with a new Cloudron install using another email address, as Cloudron rejected the one I used for the first Cloudron account, simply will not authenticate at the login -- which always appears when I click on the email icon in my second cloudron installation.
I would send mail log but you don't allow that here.
@debossnow I am sorry, despite your elaborate explanation, I am having a hard time following the issue.
Just to summarize a bit. So you have 2 Cloudrons and thus 2 different domains. Now one Cloudron works as expected, you have enabled the email server via the Cloudron dashboard, created a new mailbox and assigned one of the users of that Cloudron to be the owner of that mailbox and you can use that new mailbox email address to login to a webmailer like roundcube, installed on that Cloudron
What you said with "The second domain setup (same as first) fails consistently." raises a question, what do you mean with "same as first" ?
Doing the very same just with a different domain on a different server causes you now trouble?
Do you have any basic other non-email app installed, like surfer and are you able to login with that Cloudron user there?
Are there any errors shown in the app and mail service logs during the login with roundcube/rainloop?
I somehow don't think this is Linode related as such, but either a bug you are hitting or a missing bit of configuration on your second instance, which we have to find out.
@nebulon Thank you for taking a look!
My problem has just been solved!
It started for me because your DOCS did not make it clear that Creating a Mailbox was a whole separate Necessity even for the ADMIN. And that as an ADMIN who Added a User with the whole Email Invitation sent, user responding, creating their own Username, and Saving this DID NOT by DEFAULT at least finish the process by Adding a new mailbox corresponding to the new User .
I never guessed that THE ADMIN him or herself of the Cloudron installation would not have access AS THE ADMIN to setup Master default parameters for the Email App itself!
In your docs after following along with the entire Email setup down to the check the Status instructions at last continuing down the page it merely says, casually, as if an Option --
Mailboxes can be created for Users and Groups on a per-domain level. To do so, simply create them in the Email view.*
Mailboxes can be created for Users
when it should really be highlighted as
Now mailboxes must be set up here for your users if you intend to offer this as a feature.
Nothing indicating that we are continuing in the Enabling Emails for Users instructions or after all of the above it still won't work.
That not even the ADMIN now enacting all these steps Must manually install an Email box for him/herself.
How about "Finally, you must Finish this process by adding each User's Mailbox manually. These were not created automatically when you finished creating the User. In fact, You must first make an Email Box for yourself with Superadmin privileges or you will not be able to Login to the Email application to customize it according to your preferences.
It was finally only by reading carefully https://forum.cloudron.io/topic/4529/cloudron-email-wrong-usernam that I realized any advice I received about my email problem was ASSUMING that I knew this -- even though everytime I read your Docs I was assuming that the Mailboxes were automatically installed, certainly for the Admin first of all.
I'd recommend really emphasizing this in your docs as a clear Step 1 through Step 10(?) process REQUIRED Final step or not even the Cloudron Admin can enter his own Email installation.