Unable to configure PostgreSQL in Plesk Onyx on Ubuntu 18.04: The test connection to the database server has failed

Follow

Comments

16 comments

  • Avatar
    OHOUO YVES DANIEL

    i got the same error for UBUNTU 16.04 LTS

    i can't add and connect to postgresql server with admin user.

    0
    Comment actions Permalink
  • Avatar
    Alexandr Redikultsev

    Hello @OHOUO YVES DANIEL!

    As I can see from the screenshot, PostgreSQL 10.4 is installed on the server. I have updated the article with a little bit more details regarding this issue.

    In short, the error is actual for PostgreSQL 10 on any OS, Ubuntu 18.04 just has it out-of-the-box.

    I suggest removing PostgreSQL 10 from the server via Plesk installer and with the help of `apt purge postgresql*` command. Then, disable custom repositories and install PostgreSQL 9 that comes for Ubuntu 16.04 out of the box.

    0
    Comment actions Permalink
  • Avatar
    Oldiesmann

    Any word on when this will be fixed?

    1
    Comment actions Permalink
  • Avatar
    Alisa Kasyanova

    @Oldiesmann

    As for now, there is no exact ETA on this fix.
    You may subscribe to this article to be notified when the bug would be fixed or check our Release Notes: https://docs.plesk.com/release-notes/onyx/change-log/

    0
    Comment actions Permalink
  • Avatar
    Flinsch

    @Alexandr Redikultsev, using Ubuntu 18.04, should I install PostgreSQL 9 via Plesk or via console? Will an upgrade to PostgreSQL 10 be possible (as soon as the Plesk bug #PPPM-8775 has been fixed), without any data loss?

    0
    Comment actions Permalink
  • Avatar
    Alexandr Redikultsev

    Hi @Flinsch.

    Right now it is hard to say whether or not PostgreSQL upgrade will be supported or not, however considering the fact that the bug is already fixed in development (Plesk Onyx 17.9), I can suggest installing testing version of Plesk on some fresh non-production server, installing PostgreSQL 9 and then performing an upgrade to check how it goes. Here is the link on how to install testing version of Plesk (not for production use):

    https://support.plesk.com/hc/en-us/articles/213961885-How-to-install-older-or-testing-Plesk-versions 

    0
    Comment actions Permalink
  • Avatar
    Flinsch

    Hi @Alexandr Redikultsev, thanks for your reply. As you said, the bug is already fixed in development. So chances are good that we get the bug fix applied to our instances pretty soon? However, wouldn't it be more sensible to install PostgreSQL 10 and set the password via console? PostgreSQL should work properly, just without the comfortableness of Plesk, right? And then just wait for the bug fix in order to be able to manage it via Plesk from that moment on? Thank you very much!

    0
    Comment actions Permalink
  • Avatar
    Alexandr Redikultsev

    Hi @Flinsch.

    Currently, there is no ETA regarding the backport of the fix, so I cannot promise that it will be applied soon, but this article will be updated once it will be fixed for Plesk Onyx 17.8.

    As for your action plan, you understand it correctly, the only thing that is broken is integration with Plesk, overall PostgreSQL should work fine. 

    And most probably, once the bug will be fixed, you will be able to reset the password in the way that Plesk will accept it. No promises that it will be easy or one-click, but I think it should be possible :)

    1
    Comment actions Permalink
  • Avatar
    Alexey Kulikov

    I have just setup a fresh server with Plesk Onyx 17.8 ... cannot manage any PostgreSQL databases from the UI... as a result migrations from old servers don't work either. This Bug is actually quite critical, is there still no ETA?

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Alexey,

    The Alexandr's reply above is still actual. As soon as there will be any additional info, the article will be updated.

    0
    Comment actions Permalink
  • Avatar
    Oldiesmann

    It's been fixed in Plesk Onyx 17.9, which is in the testing stages. Check the documentation or forum for info on upgrading to it.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Oldiesmann,

    It is not recommended to upgrade production environments to preview versions (now it is 17.9).

    Preview versions are only for introductory test use. Technical issues of preview versions are not investigated by Plesk Technical Support and upgrade from Preview to stable Plesk version is also not officially supported.

    0
    Comment actions Permalink
  • Avatar
    Faust

    Hello @Ivan,

    when is the corrected version expected? Under Ubuntu 18:04 with me also the error is present. I have bought the module Postgresql fresh and can not use it. I have to pay it anyway.

    Greetings
    Faust

    0
    Comment actions Permalink
  • Avatar
    Alexandr Redikultsev

    Hi @Faust,

    This issue is fixed in upcoming Plesk Onyx 17.9 that is currently in testing.

    However, we did not have any ETA for this fix to be backported.

    0
    Comment actions Permalink
  • Avatar
    Lev Krapivner

    @Alexandr Redikultsev

    when will the next release ne released?

    I mean plesk onyx 17.9?

    any idea?

     

    0
    Comment actions Permalink
  • Avatar
    Alexandr Redikultsev

    Hi @Lev Krapivner,

    As far as I know, release is planned in the end of this year.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request