Can't login in using FQDN to the webinterface

Report bugs and workarounds
Post Reply
gojensen
Posts: 3
Joined: 07 Dec 2016 14:44

Can't login in using FQDN to the webinterface

Post by gojensen »

this may be a mailwatch issue but I'm asking here since EFA has done modifications to the entire thing... using the hyper-v image updated and has been working fine...

installed a new certificate last night (startssl.com) and during testing noticed that chrome complained about certificate name if I used just the host name in the url... https://spambox/ instead of https://spambox.domain.my/

good and well I thought and used the FQDN to try to log in... to my surprise, when I went to website it auto redirected to the bad login url...

https://spambox.domain.my/mailscanner/l ... or=baduser

I tried to log in again. but it wouldn't allow, just kept telling me "Bad Username or Password" ... I then tried to login using only hostname in the url... and after accepting the certificate error I could login just fine using https://spambox/mailscanner/login.php ...

Then I tried another browser (iexplore instead of Chrome) and ... well it seems this issue only happens in Chrome.

Anyone encountered this before? Or anything similar? I wouldn't mind too much except that the links in my emails always use FQDN so I need to edit them whenever I report a spam...
TomKarpowitz
Posts: 1
Joined: 09 Dec 2016 17:03

Re: Can't login in using FQDN to the webinterface

Post by TomKarpowitz »

I was experiencing EXACTLY the same behavior. Previously-working FQDN access to my EFA system via Chrome was redirecting to the "baduser" page, but worked perfectly in IE and Firefox.

I noticed that there was an outstanding update to Chrome waiting to be installed. I let it install the update and restart Chrome (now running at version 55.0.2883.75 m) and EFA access worked as expected once again.

Hope this works for you too...


tkarp
Post Reply