Skip to main content

CPANEL-40049 - PhpPgAdmin login fails after cPanel update

Comments

17 comments

  • cPRex Jurassic Moderator
    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
  • cPRex Jurassic Moderator
    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
  • cPRex Jurassic Moderator
    We've also created an article that signed-in users can follow along with now:
    0
  • TA
    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
  • cPRex Jurassic Moderator
    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
  • TA
    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
  • cPRex Jurassic Moderator
    This would be done from WHM >> List Accounts by clicking the cPanel icon there.
    0
  • TA
    That works! Brilliant, thank-you
    0
  • cPRex Jurassic Moderator
    Sure thing!
    0
  • TomKu
    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
  • cPRex Jurassic Moderator
    @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
  • cPRex Jurassic Moderator
    Update - I know the fix will be included in version 102, although I don't have a specific build number.
    0
  • cPRex Jurassic Moderator
    Update - this is fixed in version 102.0.6.
    0
  • tizoo
    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
  • cPRex Jurassic Moderator
    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
  • cPRex Jurassic Moderator
    Update - the fix will also be included in versions 94 and 100.
    0
  • cPRex Jurassic Moderator
    Update - the fix has been applied to version 100.0.11 and 102.0.6
    0

Please sign in to leave a comment.