Closed faip closed 1 year ago
Is the firewall blocking connections to the Internet ?
Maybe you could share the firewall settings/rules when enabled ?
Everything else is going through the firewall just fine. Here are a couple of screenshots of what I've tried.
Do you have a rule that denies everything (globally or per interface) ? What is the default action if no rule is matched ?
Is it working when you have the firewall enabled, without any rule defined ?
There is a rule at the bottom of the list that denies everything that is not explicitly allowed by another rule.
It does not work with the firewall enabled, without any rule defined.
Ok, it's hard to help without having a complete picture of the firewall config, but is the container allowed to access outgoing port 443 ?
I've opened port 443 with no success.
So after some trial and error, this is what I did to get it to work. I added a rule to the firewall, selecting from a list of built in applications. Crashplan was one of the listed applications and it was using ports 49160 and 49161. Without this rule enabled, I was unable to even log into the crashplan docker. I then moved the rule to the top of the list, giving it the highest priority. I then had to manually open TCP ports 443,4282 and 4242 with another rule. I moved this one to the top to give it the highest priority, with the previous rule moved to the 2nd highest priorty.
The CrashPlan app on the client side typically uses the following ports for communication:
TCP Port 443: The CrashPlan app uses this port for secure communication with the CrashPlan servers over SSL/TLS. It is the default port for CrashPlan's encrypted traffic.
TCP Port 4282: This port is used for communication between the CrashPlan app and the CrashPlan service running on the client machine.
TCP Port 4242: This port is used for peer-to-peer communication between CrashPlan clients when the option for local backup seeding or direct backup between computers is enabled.
I hope this helps someone in the future. Thanks for all the help jlesage!
Great that you figured it out.
For reference, ports used by CrashPlan are documented here: https://support.crashplan.com/hc/en-us/articles/9020789462669-IP-addresses-and-ports-used-by-CrashPlan
Hi jlesage,
Sorry to hassle you again. I just thought you should know that the firewall is messing with the container again. I've opened all the ports listed in the link you posted from CrashPlan. Still no luck. However, it works just fine when the firewall is turned off. I'm out of ideas.
I'm not sure if you'll see this since it's on a Closed ticket. If I don't see a response in a few days, I'll open another ticket. Thanks again for the help.
Do you still have problems with the firewall ? If yes, I suggest that you share the whole firewall configuration, for all interfaces. It would also be useful if you could share what you are trying to achieve when enabling the firewall. Finally, you might also seek help with Synology about how to use the firewall. The problem doesn't seem to be with the container, but really with the setup of the firewall.
Current Behavior
I've set up the docker container with the image from the registry. When I go to the correct url and port, I'm asked for my email (no where to enter a password). I enter my email and click Continue. Nothing happens. Then after awhile, I get an error:
Unable to sign in. Can't connect to server.
I have my Synology firewall enabled and rules set up for ports 5800, 5900 as well as the associated local ports.
I turned off the firewall and everything works as advertised. So there is something in the container or the firewall rules that is preventing the container from being able to connect with the Crashplan servers.
Does anyone have any ideas about what I may be missing?
Expected Behavior
No response
Steps To Reproduce
No response
Environment
Synology NAS DS918+ DSM7.1.1 Tried multiple browsers No reverse proxy
Container creation
Installed via image from registry.
Container log
Container inspect
Anything else?
No response