Ich habe weiterhin das Problem, das beim Aufruf der Statistiken immer ein Error 400 kommt. Dieses Problem war schon bei Version 1.2.9 vorhanden und ich dachte mit einem Update wird dies gelöst, aber schienbar nicht.
Hat jemand ähnliche Probleme?
-
-
Was steht im Log, Distro...?
-
-
-
The question here is: Can you reproduce the bug with i-MSCP 1.3.0
From my side, I cannot so... In your first post, you target the 1.2.9 version but now, in your last post, you say 1.3.0...We will not release any new version for the 1.2.x Serie. Therefore, you must either live with this bug, either fix it, either upgrade to i-MSCP 1.3.0.
BTW: When you report a problem, you must always provide us much info as possible. Your first post was not clear. Statistics can also mean access to AWStats
-
-
Hi,
i've the problem with 1.2.9 and now with 1.3.0 i've the problem too.
-
Teamviewer?
-
-
-
-
-
For those which would get the same error, you must ensure that you do not have any orphaned user (customer). You can known this by executing the following query:
Here, any user listed in the result is an orphaned and must be removed.We will provide a cleaner script for orphaned entries soon.
What about a button at admin level which would trigger a task for such a case?
- Orphaned custom DNS (no parent domain)
- Orphaned subdomain (no parent domain or domain alias)
- Orphaned domain (no parent user)
- Orphaned gui entry (no parent user)
- Orphaned mail entry (no parent domain)
- and so on...
Here, in each case, the worker (cleaner) should clean the system (orphaned vhost, orphaned maildir, orphaned webdir, orphaned homedir ...) What do you think about this?
Running that worker on update would be also valuable in my opinion.
-
-
