Currently the issue is fixed in version 96, but the developers are still discussing how to best backport the fix to version 94.
How long can we expect to wait for such a solution?
This is rather urgent what with all WHM servers on LTS no longer able to use phpMyAdmin at all for a whole year.
(Just saying "switch off IPv6" is not an acceptable workaround.)
This is rather urgent what with all WHM servers on LTS no longer able to use phpMyAdmin at all for a whole year.
(Just saying "switch off IPv6" is not an acceptable workaround.)
I'm having the same issue across all domains on my vps. One client, using ipv4 has no issues. Another client using ipv6, like me, does have the issue. However, when he goes to his cpanel using a different VPN, then he has no issues. I thought the IPs work on a different level of the protocol stack and shouldn't really be affecting the application. Waiting to hear more chatter and/or a fix.
My specs...
My specs...
- CLOUDLINUX 7.9 kvm [vps]
- v94.0.4
Last edited by a moderator:
As of this morning, I know there is a potential fix in place for version 96 which is going through the final testing. I haven't seen an update about version 94 yet as they are still working on this.
So as of right now the fix will be applied to the first release of 96, and they are still working on the 94 backport.
FYI:
If you are logged in to WHM as root and navigate to "List Accounts > cPanel (to access cPanel of the chosen account) > phpMyAdmin", no Token Mismatch error occurs, even in a IPv6 network. If you log in directly into the cPanel of that account using accounts username and password and navigate to phpMyAdmin, the error occurs.
This does not seems to make sense, but I tried this and it's being my workaround in the past weeks. Maybe this can help someone while the update is not available, or maybe this can be a hint on the solution.
If you are logged in to WHM as root and navigate to "List Accounts > cPanel (to access cPanel of the chosen account) > phpMyAdmin", no Token Mismatch error occurs, even in a IPv6 network. If you log in directly into the cPanel of that account using accounts username and password and navigate to phpMyAdmin, the error occurs.
This does not seems to make sense, but I tried this and it's being my workaround in the past weeks. Maybe this can help someone while the update is not available, or maybe this can be a hint on the solution.
Nice suggestion, though unfortunately did not work when I just tried it. (May work for others.)
The only difference is that the initial error when opening phpMyAdmin is "Bad type!" instead of "Token mismatch!", though subsequent AJAX actions and form submissions still bring the classic "Token mismatch!".
Hello @adamreece.webbox ,
Can you confirm if the same behavior exists when accessing cPanel via URL with the domain and cPanel port?(i.e. https://domain.tld:2083 )
UPDATE - while I don't have a specific version yet, I can confirm this will get backported to version 94.
Update! This is scheduled to go out in the next release of 94, which is 94.0.5. At this point I'm going to mark this one as solved.
That's a great question! It's the next minor version, so it could literally be any moment. Realistically, I would expect this to be within a week or so.
We are having exactly the same problem, worse that it took me days to discover the cause.
Waiting for a solution.
Waiting for a solution.
@Rodrigo Gomes - we pushed 94.0.5 to the Release tier yesterday, so it's likely only a few days away from being the Stable version, if that is what you're using.
I noticed our servers running LTS have received 94.0.5 automatically, and I can confirm phpMyAdmin is now very usable again over IPv6.
Obviously the lengthy delay was very disappointing, but good this is at last resolved. Thanks for pushing this fix out.
Obviously the lengthy delay was very disappointing, but good this is at last resolved. Thanks for pushing this fix out.
