Disclaimer: Using the following methods could be seen as bypassing the intent of the port restrictions set by your org.<p>I commit to github using ssh on port 443.<p><pre><code> # git remote set-url origin git@<host-in-ssh-config>:<username>/<repo>
</code></pre>
From ~/.ssh/config<p><pre><code> Hostname ssh.github.com
Port 443
User git
IdentityFile ~/.ssh/.github
</code></pre>
Consider using Dovecot on your mail server for port 443. I was not aware that Discord stopped supporting websockets over 443. I run my own Mumble voice chat server so I can put it on 443, but I understand people have a lot of friends on Discord. I am just not happy with their chat logging policy [0].<p>You could also run a proxy or VPN on port 443. You can also use sslh [1] to have SSH+SSL+Proxy+VPN all on the same port 443. You can do similar things using HAProxy + SNI + SSL, but that is a bigger subject.<p>For other things that must use other ports or protocols, you can sometimes wrap them using tsocks [2] in your VPN or SSH tunnels to port 443.<p>[0] - <a href="https://blog.discordapp.com/how-discord-stores-billions-of-messages-7fa6ec7ee4c7" rel="nofollow">https://blog.discordapp.com/how-discord-stores-billions-of-m...</a><p>[1] - <a href="https://github.com/yrutschle/sslh" rel="nofollow">https://github.com/yrutschle/sslh</a><p>[2] - <a href="https://www.redpill-linpro.com/sysadvent/2015/12/13/socks-proxy-as-poor-mans-vpn.html" rel="nofollow">https://www.redpill-linpro.com/sysadvent/2015/12/13/socks-pr...</a>