gobris wrote So, it is not controller version problem. What makes you sure about this? In past versions, controller updates needed EAP updates, too. Changes in a new controller version could also...

DocJones wrote I updated their firmware when I was still running EAP Controller locally... Ah, ok. I'm using EAC in an AWS micro instance (to keep Windows out of my office in good old tradition ;) )...

sersh wrote I don't wont to setup router from zero.... If you are sure that the username/password you entered is correct and you still can't login, then the upgrade to the new firmware doesn't...

drasche wrote On the EAP you have three form fields. One for the FROM-address, then a TO-address and the mailserver address. Ah, I see. You did try on EAP, not EAC, right? Anyway, there are bad news...

DocJones wrote it may be that the new firmware needs to be told it's connecting to an older version of the controller or else they can't communicate properly. So, firmware of the EAP should probably...

drasche wrote The form field in the EAP just does not accept the .local mail address. My EAC running on an AWS instance accepts a .local TLD w/o problems. Again: try an IP address instead of a domain...