Back to Community Threads
1
refresh-token 400 Bad Request
Problem reported by k - 8/15/2024 at 4:23 AM
Submitted
after login webmail, issue happen in 1 hour. the webmail UI is broken if press refresh, and no new mail will be notified. 
server is docker version 100.0.8979
client is win10 (1 in vm, 1 is physical pc)

* happen in http port, no reverse proxy

* with nginx, same screen like above, after re-input login url in browser:

also have tried this KB but no help. server and client timezone is UTC+8
tried clear browser cache, no help either.

client and server is in 2 different subnet, route/forward via gateway.

thanks for reading.

3 Replies

Reply to Thread
0
Tony Scholz Replied
8/15/2024 at 7:29 AM
Employee Post
Hello, 

You will also want to make sure that the time on your server is not off as well, this can break the refresh tokens. On the server open up a browser and go to https://time.is/ to check if the clock is off. 
Tony Scholz System/Network Administrator SmarterTools Inc. www.smartertools.com
0
k Replied
8/15/2024 at 6:41 PM
Hi Tony, the server is docker version. the time and date is correct.
0
Zach Sylvester Replied
8/16/2024 at 12:50 AM
Employee Post
Hey KT could you try the newest version? We just released a fix involving SignalR.

Let me know if this helps. 
Zach Sylvester Software Developer SmarterTools Inc. www.smartertools.com
Back to Community Threads

Reply to Thread

Related Knowledge Base Articles

Copy Smartermail Directories on Linux using RsyncSmarterMail > Server Configuration and Management
Force Traffic Over HTTPS when using a Reverse ProxySmarterMail > Server Configuration and Management
Multiple IIS Sites Pointing to One SmarterMail InstallSmarterMail > Server Configuration and Management
Requirements for Installation AssistanceGeneral Topics
Installation AssistanceGeneral Topics