- Veeam Support Knowledge Base
- Veeam Backup & Replication Fails to Connect to Linux Servers Due to Firewall Configuration
Veeam Backup & Replication Fails to Connect to Linux Servers Due to Firewall Configuration
| KB ID: | 2986 |
| Product: | Veeam Backup & Replication |
| Published: | 2019-08-13 |
| Last Modified: | 2022-06-16 |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Challenge
For example, distributions based on Debian, SLES, or RHEL have default firewall configurations that may block necessary connections.
Cause
Solution
Default security settings differ for each Linux OS distribution and may require additional configuration to allow connections to the required ports.
NOTE: Starting with Veeam Backup & Replication 10, the traffic port range was reduced from 2500-5000 to 2500-3300. The new port range only applies to newly deployed components after Veeam Backup & Replication 10 is installed. If an environment was upgraded from a version of Veeam Backup & Replication before 10, all existing components that were managed before the upgrade will continue to use 2500-5000.
Firewall Rules
If connections to a Linux server fail, ensure that the Linux server does not have firewall restrictions for ports 2500-3300.
If the distro uses UFW or FirewallD, remove the IPTables entry used for testing after troubleshooting is completed and integrate the ports rule into the firewall solution.
Example of Firewall wall rule configuration using iptables:
iptables -I INPUT -p tcp --dport 2500:3300 -m state --state NEW -j ACCEPTSELinux Policy
You must configure the SELinux policy to allow connections to the required range of ports. By default, the SELinux policy may restrict such connections.
If SELinux is active, you can isolate whether it is blocking connections by temporarily disabling it within the /etc/selinux/config file. After saving the file and rebooting, retest the connection. If it works after disabling SELinux, review the SELinux configuration.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
