Cannot login as Admin

esackbauer

hugalafutro Maybe for you technical gurus it’s apparent from the text, but for me (and obviously others) it is written in very obscure way.

Well I am almost 60 years and I had no problems understanding that. It was even announced in the blog before the actual update.
Maybe its because I properly read any release notes before doing any updates to critical services like mailcow, where they even put the words “Breaking changes” in bold letters…

hugalafutro

DocFraggle Maybe it’s because I’m the only user of my mail server so i never needed an “user” login. But the snippet you posted is telling nothing to layman like me, what does slash admin, slash, slash domainadmin mean? If it mentioned anything about domain in front of it I’d be in the clear.

esackbauer I too read each every changelog and this is the 1st one of mailcow I had issue with. I wouldn’t posted at all if it wasn’t for the coincidence of struggling with changes in various changelogs recently written in what I call too much of a technical mumbo jumbo.

peace out, it all works now

mlcwuser

hugalafutro Maybe it’s because I’m the only user of my mail server so i never needed an “user” login. But the snippet you posted is telling nothing to layman like me, what does slash admin, slash, slash domainadmin mean? If it mentioned anything about domain in front of it I’d be in the clea

Ok, I guess this could be improved by adding a full example URL like mail.example.tld/admin. But then putting the same thing in mailcow.conf wouldn’t have changed anything, it’s the message itself that you think should be more clear.

By the way, when I say changelogs, I’m referring to their blog. The actual full changelog with all the technical mumbo jumbo can be found here: mailcow/mailcow-dockerized2025-02 → 2025-03 😉

phil1125

DocFraggle
Yes, that will be it. I run Mailcow on ARM64, so I was still on the nightly from back in the day. Will switch to the stable now.

Happy to have this resolved, thanks everyone for staying on this and the support!

camel

Sorry, the release notes are crap!

Logins for [] have been separated:
Administrator Login: /admin

My admin user was all the time “admin”
So what about to add i have to add it to the URL ???
This prevents stupud questions from stupid users

And the “/domainadmin” does not work, it redirect to /admin/dashboard ?!?!

esackbauer

camel So what about to add i have to add it to the URL ???

This is for enhanced security. With a proper reverse proxy you can block the admin logon from the internet.
Its probably nothing “stupid users” are concerned of 😉

uniquegch

I have since today the issue not being able to login to the GUI using the administrator account. I am using also MFA, but it seems the login credentials are not correct. Also I am getting the error that I cannot send e-mails because of problem with SMTP. Sogo is disabled on m system, but I cannot login with another user, but of course only get the user options and no admin features. can I change that in the conf file?
and I installed the newest version last week and everything was fine

just used the helper script mailcow-reset-admin.sh but not able to login. it might also possible that failtoban is blocking my IP.

[unknown]
just used the helper script mailcow-reset-admin.sh but not able to login. it might also possible that failtoban is blocking my IP.

mlcwuser

uniquegch

but I cannot login with another user, but of course only get the user options and no admin features. can I change that in the conf file?

Sorry, but did you even bother to read any of the posts in this thread, especially the one marked “Best Answer”, before writing this?

If you can log in as a normal user, you are on the wrong login page. You need to go to mail.yourdomain.tld/admin in order to be able to login as admin.

uniquegch

mlcwuser yes I did and the best answer is only a link on what is new in the current version.

[unknown] I used a different computer with Firefox as browser and made sure the cache is emptied and the login with the “new” URL works. But I still have an issue sending out e-mails. Did something change regarding Port 465 SMTP out SSL/TLS. Now those accounts do have MFA. Is there a thread to that issue? can you direct me to that SMTP Sending issue thanks

mlcwuser

For me nothing has changed after the update regarding SMTP over port 465, but I don’t use MFA for my email accounts.

uniquegch Now those accounts do have MFA

Did you set up MFA for these accounts before or after you updated to 2025-03? Or let me ask a different question, did sending email ever work after you set up MFA?

If yes, then I’m not sure what caused this.

If no, then you need to set up app passwords for these accounts. This can be done by logging in to the accounts through the user login page (mail.yourdomain.tld without /admin), then go to the tab “App Passwords” and click on “Create App Password”. Alternatively, for Apple devices, you can download a profile file from the “Mailbox” tab.

oneill

esackbauer to be fair, I stood up a brand new server today and didn’t see this mentioned in the documentation anywhere.

I could have easily missed it, but I definitely wouldn’t have thought to look at the release notes for a new instance. I’ll do better next time.

accolon

oneill didn’t see this mentioned in the documentation anywhere.

See https://docs.mailcow.email/getstarted/install/#start-mailcow.

“Logins have been separated since 2025-03.”

shyevsa

I thought I have read the change log before I update,
turn out I just read the bullet list and the warning box and skipping most of the fine print.
especially the 2025-03 (Release: 25th March 2025) that don’t have any bullet list.

my fault really, and it make me realize some bad habit of mine.

« Previous Page Next Page »