Hello everyone. I have encountered a problem with my hosting. I am attempting to upload Django, and I need to connect via SSH on port 22, but it is not working. The support team suggested contacting the provider for assistance. I suspect that port 22 is blocked by the provider.

Here is what I have tried so far:
- When I tried TELNET 'host IP' 22, the connection failed. However, everything is working fine on port 21.
- I attempted the connection on a PC connected directly to the router, but still no luck.

Then, I decided to try connecting from my laptop, which was using my mobile phone's internet as a hotspot. Surprisingly, it connected successfully.
 
Now, my question is:
If the provider is indeed blocking port 22, is there any alternative way to bypass this restriction?

P.S. I apologize if my networking knowledge is limited, so please bear with me.

If your provider is indeed blocking port 22, there are a few alternative ways you can try to bypass this restriction:

1. Change the SSH listening port: By default, SSH listens on port 22, but you can change it to a different port that is not blocked by your provider. This can be done by modifying the SSH configuration file on the server.

2. Use a different protocol: SSH is not the only protocol for remote access. You can try using protocols like HTTPS or VPN to establish a secure connection with your server. This would require some configuration changes on your server.

3. Use a jump host or proxy: You can set up a jump host or a proxy server that is not blocked by your provider. You would connect to this server first and then use it as a bridge to connect to your target server. This method requires additional setup and configuration.

4. Contact your hosting provider: If none of the above methods work or if you're unsure about making these changes yourself, it's best to contact your hosting provider and explain the issue. They may be able to provide a solution or suggest alternative options.

Remember, always exercise caution when making changes to your server's configuration, and consider seeking professional assistance if you're uncertain about the steps involved.

Request the host to modify the SSH port. In case the SSH is blocked by the provider, consider switching to a different one.

Is it possible that hosting uses a different port than the standard one, hence preventing connection? It is improbable that the provider is blocking port 22.

Sometimes when setting up hosting, a non-standard port may be used instead of the default one. This could lead to difficulties in connecting to the server. However, it is highly unlikely that the service provider intentionally blocks port 22, which is the standard port for SSH connections.

Should someone arrive here from a search, I will provide the solution to this problem.

Yesterday, I spent half the night with a technical specialist trying to solve the issue of why it connects to port 21 but not port 22 using the poke method (via VPN). It became evident that the problem lies with the provider.

Today, we had an engaging and lengthy discussion with the same specialist. We resolved everything by replacing the router, and fortunately, we had a MercsisAS12 readily available.

Therefore, the solution is to either change the router or connect directly without using one.

Here are a few options you can consider if port 22 is blocked by your hosting provider:

  Use Port Forwarding: If your hosting provider allows you to configure port forwarding, you can forward a different external port (that is not blocked) to internal port 22 on your server. This way, external traffic directed to the forwarded port will be redirected to your server's SSH port. You can check your hosting provider's dоcumentation or contact their support to see if they offer this feature.

  Use a Web-based SSH Client: Some hosting providers offer web-based SSH clients that allow you to connect to your server using a web browser. These clients typically operate over port 80 or 443, which are generally open for web traffic. Check if your hosting provider offers this feature and use it as an alternative to connect to your server.

  Use SSH through a Proxy: You can try using an SSH proxy service or set up an SSH tunnel through an intermediate server. This involves establishing an SSH connection to an external server with an open SSH port and then forwarding the connection to your Django server. This method requires access to another server with an open SSH port and some knowledge of SSH configuration.

  Consider a Different Hosting Provider: If none of the above options work and your hosting provider continues to block port 22, you may want to consider switching to a different hosting provider that does not impose such restrictions. Look for providers that explicitly allow SSH access on port 22 or provide flexibility in choosing SSH ports.

  Use SSH over different protocols: SSH can use different protocols and ports, such as SSH over SSL (Port 443) or SSH over HTTP (Port 80). Check if your hosting provider supports these alternative protocols. You may need to configure your SSH server to listen on the respective ports and set up any necessary encryption or proxying.

  Use a remote desktop solution: If SSH connectivity is not possible, you can consider using a remote desktop solution like TeamViewer, AnyDesk, or VNC. These tools allow you to access your server remotely through a graphical user interface (GUI), providing similar functionality to SSH but over a different connection method.

  Consider a cloud-based development environment: If none of the above solutions work, you might consider using a cloud-based development environment like AWS Cloud9, Gitpod, or Coder. These platforms provide an integrated development environment (IDE) accessible through a web browser, eliminating the need for direct SSH access to your server.

  Use an alternative hosting service: If all else fails, you could explore alternative hosting services that offer more flexibility and fewer restrictions. Look for providers specialized in Django hosting or those that explicitly state they allow SSH connections on port 22.

  Use SSH via IPv6: If your hosting provider supports IPv6, you can try connecting to your server using SSH over IPv  This may bypass any port restrictions enforced on the IPv4 network.

  Use a different port scanning tool: Instead of using TELNET, try using a different port scanning tool, such as Nmap, to check for open ports on your server. It could provide more accurate results and help you determine if port 22 is blocked.

  Contact your internet service provider (ISP): If you suspect that your hosting provider is blocking port 22, you can contact your ISP and inquire if they block any ports by default. It's possible that your ISP itself is blocking the port, especially if you're experiencing the issue across multiple devices.

  Enable SSH access through a control panel or firewall: Some hosting providers provide control panels or firewall settings that allow you to explicitly enable SSH access or open specific ports. Check if your hosting provider offers such features and configure them accordingly.

  Configure SSH to listen on additional ports: In addition to port 22, you can try configuring your SSH server to listen on additional ports that are not blocked by your hosting provider. This can be done by modifying the SSH server configuration file (sshd_config) and specifying the desired ports.

  Use a third-party SSH tunneling service: There are third-party SSH tunneling services available that can help you bypass port restrictions. These services act as intermediaries, allowing you to connect to your server through their servers. However, be cautious when using such services and ensure they are reputable and trustworthy.

If your router supports it, you can forward another open port (e.g., 2222) to your server's port 22. This involves configuring your router and server, but it's a legitimate workaround.

SSH Tunneling: You can use SSH tunneling to encapsulate your SSH connection within an HTTP or HTTPS connection. This might bypass the port 22 restriction. Tools like sshuttle or ngrok can help with this.

VPN: Connect to a VPN service before attempting to SSH into your server. This changes your IP address and might help you bypass the restriction.

However, if your provider is blocking port 22, it's likely due to security concerns or to prevent unauthorized access.