You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of a note for other users as I solved the problem.
My docker-skype instance was working fine, after I resumed from a suspend skype would not reconnect. I logged out of skype and tried to log back in and skype would fail with a "could not connect" message. I deleted the container and then the image and it still would not connect.
I then remembered I disabled my local firewall (firehol) for other work. It turns out that I had to restart the docker service after firewall changes were made to get docker-skype to connect again.
The text was updated successfully, but these errors were encountered:
Docker makes changes to the firewall tables when new containers are create and so on. Reloading the firewall rules can result in the docker installed rules to go away. I have the following rule added -A POSTROUTING -s 172.17.0.0/24 ! -d 172.17.0.0/24 -j MASQUERADE that resolves the issue for me, where 172.17.0.0/24 is the address space of the docker0 network.
This is more of a note for other users as I solved the problem.
My docker-skype instance was working fine, after I resumed from a suspend skype would not reconnect. I logged out of skype and tried to log back in and skype would fail with a "could not connect" message. I deleted the container and then the image and it still would not connect.
I then remembered I disabled my local firewall (firehol) for other work. It turns out that I had to restart the docker service after firewall changes were made to get docker-skype to connect again.
The text was updated successfully, but these errors were encountered: