A note for anyone who finds themself here: This may be due to my inexperience with Docker perhaps but I had issues getting this working. The issue is 100% on the side of my network somewhere, but for some reason I'm not able to get this to connect to my Roundcube instance if it's sending a request to $mailcow_hostname. I am using Mailcow on a VM under Proxmox and was only able to resolve my issue by replacing the mailcow hostname with the IP address of the VM it's running on. If anyone has any idea how to fix this 'the right way' let me know, but this is how I dealt with the error 'Unable to get token, is your RC link correct?', as requests to the hostname were timing out.

I have the same issue "'Unable to get token, is your RC link correct?' However I didn't figure out where exactly to replace the $mailcow_hostname with the ip address. Mailcow is running on a linux surver in a docker stack, roundcube is also running in a different docker container.

Admin can't login to the Roundcube user who has activated 2FA using roundcube plugin twofactor_gauthenticator. Please modify this admin login script so when admin enables 2FA for mailboxes and admin logoin to roundcube from Mailcow admin dashboard, it should not ask for 2FA code.

When using Mailcow 2025 behind a reverse proxy (e.g. Nginx via CloudPanel), the following URL construction may cause issues: $url = "https://$mailcow_hostname:" . $_SERVER['SERVER_PORT'] . $rc_path; In my setup, removing the port part entirely solved the problem: $url = "https://$mailcow_hostname" . $rc_path; Including $_SERVER['SERVER_PORT'] can break redirects or token handling, especially when the internal port (e.g. 7443) differs from the external port exposed by the proxy (usually 443). Let the proxy handle the port translation.