WEB mail problem after upgrade
-
Hi
I upgraded my mdaemon to version 23
After that is get this errors when I try to open WebMail on Android devices:
the request was invalid .
if you need assistance please contact your email administrator
then I look the web mail LOG. I see this log line :
WCAPI - Downgrade request attempted to Domain mydomain.com from origin (https://mydomain.com)
how can I solve this problem ?
-
What version of MDaemon did you upgrade from?
Are you using HTTP or HTTPS when attempting to open webmail?
Do you have the issue with any other devices or browsers?
Have you cleared the cache and restarted the android device?
What version of Android is being used?
-
I'm having the same problem, same error message
I've tried both http and HTTPS
I've tried with a tablet running Android 12 and a mobile running Android 13
I have cleared cache and restarted both devices
-
I upgraded from version 21 to 23.
if the browsers agent is android,then the webmail stop the user at login page.
-
Please try setting the following in the [Default:Settings] section of the MDaemon\WorldClient\Domains.ini
WorldClientAPI:AllowHttpsToHttpDowngrades=Yes
Save the file, and then restart webmail.
Are you able to open webmail on the android devices after restarting?
-
no. same error.
-
@hamed
Are you using HTTP or HTTPS when attempting to open webmail?
Do you have the issue with any other devices or browsers?
Have you cleared the cache and restarted the android device?
What version of Android is being used?
Is there a proxy or any other devices between the Webmail server and the Android device that may be altering the requests and responses?
Is webmail running via its own webserver or via IIS?
Please post the entire session from the log that shows an Android device connecting and attempting to login.
-
@Arron
Hello,I am experiencing the identical issue. Adding the parameter WorldClientAPI:AllowHttpsToHttpDowngrades = Yes to MDaemon\WorldClient\Domains.ini had no effect.
MDaemon is placed behind an Nginx reverse proxy. WorldClient is running on its native integrated web server (not IIS).
From desktop browsers, WorldClient loads and functions correctly. From Android mobile devices (Chrome browser), access fails with an error.
Relevant log entry from WorldClient logs:
-
@Nur
What version of MDaemon are you using?
What section in the Domains.ini file did you add WorldClientAPI:AllowHttpsToHttpDowngrades = Yes to?
Please post the entire session from the log that shows an Android device connecting and attempting to login.
If the android device bypasses the reverse proxy, does it work correctly?
Are you using HTTP or HTTPS when attempting to open webmail?
Do you have the issue with any other devices or browsers?
Have you cleared the cache and restarted the android device?
What version of Android is being used?
-
@Arron
What version of MDaemon are you using?
v.21.5.3
What section in the Domains.ini file did you add WorldClientAPI:AllowHttpsToHttpDowngrades = Yes to?
[Default:Settings]Please post the entire session from the log that shows an Android device connecting and attempting to login?
I only see this log in webmail.log: WCAPI - Downgrade request attempted to Domain mydomain.com from origin, host (mydomain.com), referrer (mydomain.com/webmail/logon). IP (local IP of nginx)If the android device bypasses the reverse proxy, does it work correctly?
When I try to connect without reverse proxy using HTTP it works.Are you using HTTP or HTTPS when attempting to open webmail?
To connect to nginx I am using HTTPS. Between nginx and MDaemon is HTTP.Do you have the issue with any other devices or browsers?
Only with mobile devices.Have you cleared the cache and restarted the android device? What version of Android is being used?
I checked several devices, same problem (13, 14 Android).
-
Support for WorldClientAPI:AllowHttpsToHttpDowngrades wasn't added until MDaemon 23.0.2.
You can upgrade to an MDaemon version newer than 23.0.2, preferably the latest version which is 25.5.2, which supports allowing HTTP downgrades. Or change your proxy to not downgrade the sessions.
I suspect you are only reporting the issue on mobile devices because only mobile devices are using the PRO theme. You will likely also see the issue from any browser attempting to access the PRO theme.


