After upgrade Mailcow to ver. 2025-03 and when try to run test for an adding transport on routing it comes up with an 404 Not Found error (Nginx)
Anyone else get this message after upgrade to 2025-03?

I just installed Mailcow, but with the previous version where the transport test worked. Since then I have upgraded to 2025-3. After working on another problem with DNS, I tried a few things to see if my resolution problem was fixed, and this transport page was one of them. I was starting to think I broke something with unbound, but all my other DNS issues seem to be resolved, yet this page now gives the 404 error.
So yes, I’m having the same issue.

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

When you have a look via the browser’s developer tools (F12 in Chrome i.e., Network tab), you can see that this URL (I changed it to not contain sensible data) is causing the 404:

https://your.mailserver.tld/admin/inc/ajax/transport_check.php?transport_id=1&transport_type=transport-map&mail_from=test%40test.de&mail_rcpt=null%40hosted.mailcow.de&csrf_token=XXXXXXX

The problem here is the new /admin prefix of the URL, it seems the Mailcow team didn’t adjust it accordingly. If you copy the URL, remove “/admin” from it and use the result in your browser, it works.

    DocFraggle
    Yes i try this now to and it is working when do so.
    I hope the Mailcow team can come up with a solution and an update to make this work again and that they are aware of this bug.

        No one is typing