Beberapa minggu belakangan ini Balifiber mulai memblokir koneksi ke port 22 (port SSH) (Outgoing), udah coba konfirmasi belum ada kejelasan sampai hari ini. Bagi anda yang menggunakan koneksi Balifiber untuk sementara bisa menggunakan solusi jump host ataupun menggunakan VPN.
Solusi lainnya adalah mengganti port 22, contoh saya tes menggunakan port 2222, langsung bisa terkoneksi.
Log
Contoh log koneksi timed out.
> ssh root@koneksi.jaranguda.com -vvv OpenSSH_8.1p1, OpenSSL 1.1.1d FIPS 10 Sep 2019 debug1: Reading configuration data /home/tommy/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug3: /etc/ssh/ssh_config line 51: Including file /etc/ssh/ssh_config.d/05-redhat.conf depth 0 debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf debug2: checking match for 'final all' host koneksi.jaranguda.com originally koneksi.jaranguda.com debug3: /etc/ssh/ssh_config.d/05-redhat.conf line 3: not matched 'final' debug2: match not found debug3: /etc/ssh/ssh_config.d/05-redhat.conf line 5: Including file /etc/crypto-policies/back-ends/openssh.config depth 1 (parse only) debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config debug3: gss kex names ok: [gss-gex-sha1-,gss-group14-sha1-,gss-group1-sha1-] debug3: kex names ok: [curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1] debug1: configuration requests final Match pass debug1: re-parsing configuration debug1: Reading configuration data /home/tommy/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug3: /etc/ssh/ssh_config line 51: Including file /etc/ssh/ssh_config.d/05-redhat.conf depth 0 debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf debug2: checking match for 'final all' host koneksi.jaranguda.com originally koneksi.jaranguda.com debug3: /etc/ssh/ssh_config.d/05-redhat.conf line 3: matched 'final' debug2: match found debug3: /etc/ssh/ssh_config.d/05-redhat.conf line 5: Including file /etc/crypto-policies/back-ends/openssh.config depth 1 debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config debug3: gss kex names ok: [gss-gex-sha1-,gss-group14-sha1-,gss-group1-sha1-] debug3: kex names ok: [curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1] debug2: resolving "koneksi.jaranguda.com" port 22 debug2: ssh_connect_direct debug1: Connecting to koneksi.jaranguda.com [52.221.1.22] port 22. debug1: connect to address 52.221.1.22 port 22: No route to host ssh: connect to host koneksi.jaranguda.com port 22: No route to host
Beberapa provider cloud yang dicoba Amazon AWS, Digital Ocean, Vultr, Linode dan Upcloud.
Bila perkerjaan atau kegiatan anda bergantung ke internet saatnya mengganti Balifiber dengan alternative lain
Barusan saya ketemu hal yang sama mas. Provider internet yang saya pakai memblok akses ke port 22 server manapun. Ternyata ada laporan dari para penyedia hosting, katanya banyak yang menyerang/flood ke port 22 mereka dari provider internet tersebut.
Jadi perubahan aturan di provider internet tersebut, bahwa port 22 memang diblok oleh mereka. Untuk akses SSH ke server, pakai port lain.