board: Problem with Restya via Docker and Plesk

I have a Problem with Restyaboard on Docker and Plesk. I’ve installed Restyaboard and PostgreSQL via Docker on my Server with Plesk and now I have one major problem. The console of Restyaboard says:

sed: -e expression #1, char 73: unknown option to `s’

the console of Postgres says:

2020-03-31 16:41:17.991 UTC [107] LOG: invalid length of startup packet

What can I do? Thanks for Helping

My Hardware and Software: Intel® Xeon® CPU E5-2630 Plesk Obsidian v18.0.25_build1800200325.19 os_Ubuntu 18.04 Ubuntu 18.04.4 LTS Hosted at Strato Germany

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 31 (17 by maintainers)

Most upvoted comments

Not sure how deployment is done in plesk.

You could try following:

Change the host and port like this

- POSTGRES_HOST=h2872773.stratoserver.net
- POSTGRES_PORT=5433
- POSTGRES_USER=postgres
- POSTGRES_PASSWORD=password1
- POSTGRES_DB=restyaboard

or if it set up like a docker-compose and therefore internal docker referencing works you could try following (use containername as host and internal port). Maybe you could check through the docs if in plesk the deployed container share a network or similiar.

- POSTGRES_HOST=postgres
- POSTGRES_PORT=5432
- POSTGRES_USER=postgres
- POSTGRES_PASSWORD=password1
- POSTGRES_DB=restyaboard

BlackDark on Apr 6, 2020

Ah this could be probably caused by the POSTGRES_HOST. Could you remove the trailing / and check if its working then?

BlackDark on Apr 5, 2020

https://docs.plesk.com/de-DE/obsidian/administrator-guide/75823/#container-settings

BlackDark on Apr 4, 2020

No i mean the variables you have to specify for restyaboard: https://github.com/RestyaPlatform/board/blob/dev/docker-compose.prod.yml#L6

      - POSTGRES_HOST=postgres
      - POSTGRES_USER=admin
      - POSTGRES_PASSWORD=admin
      - POSTGRES_DB=restyaboard

how do they look like in your deployment? or didn’t you set them?

BlackDark on Apr 3, 2020

@KarlFrederik do your postgres variables contain /? This probably breaks the sed command in the startup script

BlackDark on Apr 3, 2020