Portainer Documentation
Official WebsiteGet 5 Nodes of BE Free
Search…
CE 2.11
Welcome
Release Notes
Getting Started
Introduction
Portainer architecture
Requirements and prerequisites
Install Portainer CE
Upgrading Portainer
Using Portainer
Home
Docker/Swarm
Kubernetes
Azure ACI
Edge Compute
Account settings
Administering Portainer
Users
Environments
Registries
Authentication logs
Settings
Frequently Asked Questions
Portainer Concepts
Installing
Upgrading
Troubleshooting
My Portainer Extensions license has expired. What can I do?
Why can't my users see anything in the environment they have access to?
How do automatic updates for stacks/applications work?
Can I build an image while deploying a stack/application from Git?
Why don't custom standalone app templates show when using Docker Swarm?
Why can't my agents communicate with Portainer on Swarm?
Known issues with VMware
Can you view deleted container logs in Portainer?
I enabled "Force HTTPS only" and now I'm locked out of Portainer. How do I get back in?
Exposed ports in the container view redirect me to 0.0.0.0. What can I do?
How can I get the logs for Portainer itself?
How can I switch back to internal authentication?
How do I reset my Portainer password?
Slow Overlay Network?
Contributing
Advanced Topics
CLI configuration options
App templates
The Portainer Edge Agent
Access control
Reset the admin user's password
Security and compliance
Using your own SSL certificate with Portainer
Using Portainer with reverse proxies
Helm chart configuration options
Deprecated and removed features
API
Accessing the Portainer API
API documentation
API usage examples
Get More Help
YouTube
Slack
Discord
Contribute to Portainer
Contribute
Build instructions
Powered By GitBook
Slow Overlay Network?
Slow network connectivity using Overlay Networks in your swarm clusters using VMs for node? GRO(Generic Receive Offload) or RSC (Receive Segment Coalescing) might be to blame.
If you are running Virtualised Linux with latest 5+ Kernel for your Swarm nodes you may run into this issue.
You need to check GRO / RSC settings on your Hypervisor's network interface or vSwitch. Relevant issues reported at moby/moby here and here.

Linux Based Hypervisor's

Run the following command to get the status of GRO for your network interface
ethtool -k <interface name> | grep generic-receive-offload
You can turn GRO off by running the following command
ethtool -K <interface name> gro off
Repeat for all required interfaces. This should improve the network speeds for for your overlay networks between swarm node VMs
​

Hyper-V

Run the following command to get the status of RSC for your network interface
Get-VMSwitch -Name <vSwitchName> | Select-Object *RSC*
​
​
You can turn RSC off by running the following command
Set-VMSwitch -Name <vSwitchName> -EnableSoftwareRsc $false
Repeat for all required interfaces. This should improve the network speeds for for your overlay networks between swarm node VMs.
Previous
How do I reset my Portainer password?
Next - Frequently Asked Questions
Contributing
Last modified 5mo ago
Copy link
Edit on GitHub
Outline
Linux Based Hypervisor's
Hyper-V