Install the app
How to install the app on iOS

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

My containers don't want to talk to each other. What am I missing?

As an Amazon Associate, we may earn commissions from qualifying purchases. Learn more...

488
98
NAS
DS220+, DS918+, RS1219+
Operating system
  1. Windows
Mobile operating system
  1. Android
I've been working on getting PhotoPrism and Paperless up and running with my brother in law for the last couple weeks off and on. My BIL is a sharp dude who works with containers and docker for a living. We cannot get PhotoPrism to talk to MariaDB and we cannot get Paperless to talk to Redis. He has taken the docker-compose files from my NAS and tried them on his own non-synology environment and they are working fine. Are we missing some sort of Synology firewall setting or something that is blocking communication from the app container to the database containers? Is there any way my ubiquiti firewall is somehow blocking communication?
 
Solution
Turn off the firewall and try. If it works, then all you need to do is add an “allow” for that particular subnet.
Turn off the firewall and try. If it works, then all you need to do is add an “allow” for that particular subnet.
 
Upvote 0
Solution
Turn off the firewall and try. If it works, then all you need to do is add an “allow” for that particular subnet.
We've tried adding an allow. I might temporilly disabled the entire syno firewall and see what happens. Maybe we are missing something with the net.
 
Upvote 0
Probably unrelated, but my Docker bridge network corrupted a day or so ago, so containers that used to address one another are badly broken. I'm getting concerned that Synology is giving us "silent" update patches which are futzing with everything.
 
Upvote 0
Disabling the firewall completely allowed document upload in paperless. The redis container must be on a different subnet that what we think it is. Will have to do more investigating.
 
Upvote 0
A quick way is to go Docker > Network to check the subnet used by each container.
 
Upvote 0
It looks like we have the correct subnet, but I must have set up the firewall rule incorrectly. Probably going to work with my BIL again in a day or two, we'll check it out then. Thanks.
 
Upvote 0
Probably unrelated, but my Docker bridge network corrupted a day or so ago, so containers that used to address one another are badly broken. I'm getting concerned that Synology is giving us "silent" update patches which are futzing with everything.
Your probable problem is IPTables being messed up. 99% sure we are not getting silent updates.
 
Upvote 0

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.

Popular tags from this forum

Similar threads

Best practice to avoid problems like these when using or testing apps in ones LAN Network is to grant...
Replies
19
Views
1,630
  • Question Question
Do realize, that enabling any user to run docker containers is largely the same as giving that user full...
Replies
6
Views
1,937

Thread Tags

Tags Tags
None

Welcome to SynoForum.com!

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

Registration is free, easy and fast!

Trending content in this forum

Back
Top