CPANEL-40049 - PhpPgAdmin login fails after cPanel update
When logging into phpPgAdmin through cPanel I'm repeatedly getting 'Login failed'. This error only started today (after upgrading cPanel to v100.0.10). Previously I have had no problems accessing phpPgAdmin.
However I have tried to trouble-shoot, doing the following:
- WHM >> SQL Services >> Configure PostgreSQL >> Install Config & Create Users
- set listen_addresses = '*' in /var/lib/pgsql/data/postgresql.conf
- added 'local all all trust' and 'host all all 127.0.0.1/32 trust' in /var/lib/pgsql/data/pg_hba.conf
(all the above followed by postgresql service restarts)
I am not sure where to proceed from here - can someone provide suggestions?
(phpPgAdmin 5.6, PostgreSQL 9.2, PHP 7.3)
-
Hey there! We're aware of an issue with this and we're working on it now. I'll post an update as soon as I have one! 0 -
We've created case CPANEL-40049 for our developers to look into this issue. I'll be sure to post an update as soon as I have one. 0 -
Thanks for the quick response. The article states " If you access the cPanel account using a root generated session, you will not encounter this problem. " - how do I do this? I need a work-around in the short term. 0 -
That means that if you access WHM first, and then cPanel, you won't run into the issue. The issue is specifically with the cPanel user session. 0 -
How do I access cPanel from WHM? Currently I log into WHM at my_server_url:2087 (logging in as root) and cPanel at my_server_url:2083 (logging in as a cPanel user). Switching ports ends the session. I can't find anywhere allowing me to log in to cPanel as root - did find this article which says you can't: 0 -
This would be done from WHM >> List Accounts by clicking the cPanel icon there. 0 -
That works! Brilliant, thank-you 0 -
Sure thing! 0 -
The workaround in case CPANEL-40049 suggests using root account. Well, root does not need phppgadmin to access postgres. Regular users prefer phppgadmin and they are still complaining. Its 2 days already. Please start fixing it. 0 -
@TomKu - we already have the case open and the developers are testing a possible fix. I'll be sure to post updates as I get them. 0 -
Update - I know the fix will be included in version 102, although I don't have a specific build number. 0 -
Update - this is fixed in version 102.0.6. 0 -
Update - this is fixed in version 102.0.6.
Thanks cPRex ! Any chance this gets fixed in 100.0.x as well? or is the best course of action to allow the update to "CURRENT" on affected servers?0 -
We've reached out to the developers to see what their plan is for version 100 but haven't heard anything yet today. It's still early here so I'll keep you updated. 0 -
Update - the fix will also be included in versions 94 and 100. 0 -
Update - the fix has been applied to version 100.0.11 and 102.0.6 0
Please sign in to leave a comment.
Comments
17 comments