Restyaboard - self-hosted, open source, Trello like kanban board

Docker Restyaboard - self-hosted, open source, Trello like kanban board

Currently reading
Docker Restyaboard - self-hosted, open source, Trello like kanban board

Rusty

Moderator
NAS Support
4,378
1,269
www.blackvoid.club
NAS
DS718+, DS918+, 2x RS3614RPxs+
Router
  1. RT1900ac
  2. RT2600ac
  3. MR2200ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
Thank you. I tried it and received the following:
Code:
[email protected]:~# docker exec -it restyaplatform-restyaboard1 /bin/bash
[email protected]:/usr/share/nginx/html# ping postgres
PING postgres (172.17.0.2): 56 data bytes
64 bytes from 172.17.0.2: icmp_seq=0 ttl=64 time=0.191 ms
64 bytes from 172.17.0.2: icmp_seq=1 ttl=64 time=0.096 ms
64 bytes from 172.17.0.2: icmp_seq=2 ttl=64 time=0.100 ms
#and so on#
[email protected]:/usr/share/nginx/html# nc -zv postgres  5433
bash: nc: command not found

Besides that the nc command is not yet in the container (could I fix this?), there are two things that I am the whole time really wondering about:
  1. Although I changed the restya environment variable POSTGRES_PORT to 5433, the terminal output always tells me: "[...] Is the server running on host [...] and accepting TCP/IP connections on port 5432?" Didn't restya get it that I changed this port number?! Or is this just a stadard error message that doesn't adjust the used port number?
  2. In the pgadmin statistics table, my "restya" database is listed with the client address "172.17.0.1/32:56607" although I specified a different host IP in the restyas' database's server settings (there I inserted my NAS address like you described). In the ping result above, I also got a 172.17.... address, but a different one. I am confused. Doesn't this mean that my restya environment variable POSTGRES_HOST also should be this 172.17... address?
Thank you
This means that the communication between the containers is working fine and that’s ok.

considering that you are using nas ip address as your postgres host, now you need to make sure that postgres is available on your network on that custom port 5433.

you can test it from your PC. Depending on your OS you can run the same command as before (nc) just change the destination to your nas ip address instead of the container name. Use that command if you are a mac or linux user.

If you are a win user open up command prompt and try this:

telnet nas ip address 5433

if you get info that telnet is missing you can install it using the Windows features options in add remove programs. Telnet client that it. Then try again.

getting a black screen with the telnet command will mean that postgres is running on that port
 
6
0
NAS
DS1817+
Last edited:
Yes I am getting a black screen with blinking cursor. With other, not assigned, port numbers I get an error in return.

What then could be the issue? Could it be one of those I thought about in my last post - basically that Restya still tries to communicate over 5432?
  1. Although I changed the restya environment variable POSTGRES_PORT to 5433, the terminal output always tells me: "[...] Is the server running on host [...] and accepting TCP/IP connections on port 5432?" Didn't restya get it that I changed this port number?! Or is this just a stadard error message that doesn't adjust the used port number?
  2. In the pgadmin statistics table, my "restya" database is listed with the client address "172.17.0.1/32:56607" although I specified a different host IP in the restyas' database's server settings (there I inserted my NAS address like you described). In the ping result above, I also got a 172.17.... address, but a different one. I am confused. Doesn't this mean that my restya environment variable POSTGRES_HOST also should be this 172.17... address?
 

Rusty

Moderator
NAS Support
4,378
1,269
www.blackvoid.club
NAS
DS718+, DS918+, 2x RS3614RPxs+
Router
  1. RT1900ac
  2. RT2600ac
  3. MR2200ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
Yes I am getting a black screen with blinking cursor.
Postgres is fine then

What then could be the issue?
Try and use for the POSTGRES_HOST variable, the name of your postgres container, not the IP address of the NAS. Internal Docker DNS should make them visible in the same network. Try and see if that will fix the problem.
 
1
0
NAS
DS218+
Last edited:
Hello,
i just tried to follow these steps above, but all I get is a
Code:
psql: could not connect to server: Connection refused
    Is the server running on host "192.xxx.xxx.xxx" and accepting
    TCP/IP connections on port 5432?

my settings are:

restyabord-Container:
Port-Einst.
Lokal: 8077
container:80

postgres-Container:
Port-Einst.
Lokal: 32770
Container: 5432
Envirement:
POSTGRES_PORT: 32770
POSTGRES_HOST: 192...__local_IP_NAS

server and database succesfully added in/ with pgadmin4
all containers are running properly, but if I try to run restyaboard in Firefox with http://192_my_local_NAS_IP_:8077
nothing happens (connection failed)

edit:
just did a telnet terminal over windows:
telnet IP_my_NAS 5432
->connection failed

edit_2:
used the POSTGRES_HOST variable the name of my postgres container
->
psql: could not translate host name "postgres1" to address: Name or service not known

what the heck have I to do to get that thing running... my head is smoking ;-)
Thanks in advance
regards
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

I'll delete everything I can containers/images/etc, and start fresh over the weekend. While I really like...
Replies
48
Views
1,958
I don’t understand what you mean by ‘defaults to Port 5001’. If you use the URL without a port number then...
Replies
53
Views
3,711
I ran across a very complete how-to-install-nextcloud on Docker using the Synology UI (just the UI, not...
Replies
28
Views
4,645
I found a way to do this using portainer and stacks. DB Stack is a great source for all things docker.
Replies
33
Views
9,703
yes I have made the switch over. The only thing I had to do was create a new container. I had to refer...
Replies
265
Views
47,864

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Top