I have done below mentioned things and it started working. vim ~/.ssh/config Add these lines and save it. Host bitbucket.org Hostname altssh.bitbucket.org Port 443 For Windows: Go to the place where your .ssh folder is located (run %USERPROFILE%). open the .ssh folder and create a file with the name config without any extension. Paste the … Read more
Try adding the table name explicitly: iptables -t nat -D POSTROUTING 1
From the netfilter FAQ: The answer unfortunately is: No. Now you might think ‘but what about libiptc?’. As has been pointed out numerous times on the mailinglist(s), libiptc was NEVER meant to be used as a public interface. We don’t guarantee a stable interface, and it is planned to remove it in the next incarnation … Read more
I had the same problem with Debian 8. I fixed it by restarting the system. It seems that the error can occur if the kernel image was updated and the system was not restarted thereafter.
In Omnibus-packaged versions you can modify that property in the /etc/gitlab/gitlab.rb file: gitlab_rails[‘gitlab_shell_ssh_port’] = 766 Then, you’ll need to reconfigure GitLab: # gitlab-ctl reconfigure Your URIs will then be correctly displayed as ssh://git@git.domain.com:766/group/project.git in the web interface.
From iOS 10.3 you also need to go to Settings > General > About > Certificate Trust Settings and trust Charles certificate.
the best way is to restart your docker service, then it’ll re-add your docker rules to iptables. (on deb-based: sudo service docker restart) however, if you just want to restore those rules without restarting your service, i saved mine so you can inspect, and adjust it to work for you, then load using sudo iptables-restore … Read more
I faced the same problem in a docker-compose setup. 1. Clear all chains: sudo iptables -t filter -F sudo iptables -t filter -X 2. Then restart Docker Service: systemctl restart docker
Thanks for the help everyone! Turns out that it was an iptable conflict. Two rules listing the port open (which resulted in a closed port). However, one of the comments by aka and another by manu2013 were problems that I would have run into, if not for the conflict. So! Always remember to edit the … Read more
This question should be on Server Fault. Nevertheless, the following should do the trick, assuming you’re talking about TCP and the IP you want to allow is 1.2.3.4: iptables -A INPUT -p tcp –dport 8000 -s 1.2.3.4 -j ACCEPT iptables -A INPUT -p tcp –dport 8000 -j DROP