NOT WORKING Adding PostgreSQL (pgsql) via UI at opal6

mattez

I am unable to add new PSQL database via UI at https://my.opalstack.com/database/new/?type=pgsql
When I try to submit form nothing happens. No error. No notice. Nothing.

Server: opal6.opalstack.com
I tested this in Chrome and Firefox. Same.
Adding a new MariaDB is working fine.

Anybody experiencing same behavior?

US support is now offline - I understand it is early morning.
I am just starting to migrate stuff from Webfaction and this is a second time in short period when something is not working here. 🙁 First one was this (hours of downtime): https://community.opalstack.com/d/266-502-bad-gateway-in-opal6

Really hope 24/7 coverage come soon.

sean

Please check https://my.opalstack.com/psqlusers/ and ensure that you do not have a pre-existing PostgreSQL user with the same name as the database that you are trying to create.

If you see one there, delete it completely and then try creating your database again.

Please try it out and let me know how it goes, thanks!

mattez

sean thank you for your guidance. I just checked it and, unfortunately, there is no existing user with name corresponding to DB name which I am trying to create.

To be sure I tried to create new PSQL DB again just now with the same result = no success, no error, nothing is happening

mattez

And one side note about UI:
During testing, I created one MariaDB and one user. This process created a message in "Notices" and also show some success message as "snackbar". This is what I expected and I appreciated and like that actions history in "Notices". But..
When I start to clean it up and I marked that DB for deletion, there was no message in "Notices" created and no message as "snackbar" shown about that it was successfully mark for deletion in 24hrs.
It would be nice to have consistency in UI behavior. And have record in "notices" about deleting DB.
I know it is icing on the cake. 😃

sean

mattez we hope to have more/better notifications in the dashboard UI in the future.

I responded to your email about this issue earlier, please follow up there if you need further assistance. Thanks!

sean

This turned out to be caused by an existing PostgreSQL database owned by another customer on the shared server that had the same name as the database that @mattez was trying to create. We'll have better UI feedback for this problem in the future.