Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
25% Recurring Discount on NVMe VPS
Try EnsoVPN - Reliable VPN - 1-Day Free Trial
K.N Cloud — High-Performance KVM VPS in Miami,Frankfurt and Amsterdam
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
CloudLinux
Try EnsoVPN - Fast & Private VPN - 1-Day Free Trial

Categories

In this Discussion

Home › Help
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Why I cannot sshd to My Dedirock VPS ?

wisepandawisepanda Member
in Help

From one hour ago until now, SSH connections to the server are not allowed.

Local ident: 'SSH-2.0-ssh2js1.16.0'
Client: Trying 104.168.74.xx on port xxxx ...

Timed out while waiting for handshake

https://billing.dedirock.com/clientarea.php
This page shows me my VPS is running/online.

Need HELP.

«1

Comments

  • wisepandawisepanda Member

    @DediRock

    Thanked by 1DediRock
  • stablecloudstablecloud Member, Patron Provider

    Let me check my crystal ball.

    Have you tried contacting dedirock?

    Thanked by 5wisepanda NotFoundException BasToTheMax Nekopara gbzret4d
  • wisepandawisepanda Member

    @stablecloud said:
    Let me check my crystal ball.

    Have you tried contacting dedirock?

    I am doing that now.

  • wisepandawisepanda Member

    https://tcp.ping.pe/
    Query: tcp 104.168.74.XX:80
    
    Location ISP TCP port check result
    Canada, BC, Vancouver Shaw Connection to 104.168.74.XX:80 failed
    Canada, BC, Vancouver Hurricane Connection to 104.168.74.XX:80 failed
    USA, CA, Fremont Hurricane Connection to 104.168.74.XX:80 failed
    USA, CA, Fremont IT7 FMT2 Connection to 104.168.74.XX:80 failed
    USA, CA, Fremont Linode Connection to 104.168.74.XX:80 failed
    USA, CA, San Francisco Digital Ocean Connection to 104.168.74.XX:80 failed
    USA, CA, Santa Clara Hurricane Connection to 104.168.74.XX:80 failed
    USA, CA, Los Angeles Hurricane Connection to 104.168.74.XX:80 failed
    USA, CA, Los Angeles Vultr Connection to 104.168.74.XX:80 failed
    USA, CA, Los Angeles NetActuate Connection to 104.168.74.XX:80 failed
    USA, CA, Los Angeles Freakhosting Connection to 104.168.74.XX:80 failed
    USA, WA, Seattle Google Connection to 104.168.74.XX:80 failed
    USA, UT, Salt Lake City Evolushost Connection to 104.168.74.XX:80 failed
    USA, CO, Denver NetActuate Connection to 104.168.74.XX:80 failed
    USA, TX, Fort Worth AT&T Connection to 104.168.74.XX:80 failed
    USA, TX, Dallas NetActuate Connection to 104.168.74.XX:80 failed
    USA, TX, Dallas Freakhosting Connection to 104.168.74.XX:80 failed
    USA, TX, Houston Cubepath Connection to 104.168.74.XX:80 failed
    USA, MO, Kansas City Rozint Connection to 104.168.74.XX:80 failed
    USA, IL, Chicago NetActuate Connection to 104.168.74.XX:80 failed
    USA, IL, Chicago Infraly Connection to 104.168.74.XX:80 failed
    USA, IL, Chicago Teracast Connection to 104.168.74.XX:80 failed
    USA, MI, Grand Rapids RackGenius Connection to 104.168.74.XX:80 failed
    USA, MI, Southfield Interconnecx Connection to 104.168.74.XX:80 failed
    USA, FL, Miami Goodleaf Connection to 104.168.74.XX:80 failed
    USA, FL, Miami Cubepath Connection to 104.168.74.XX:80 failed
    USA, FL, Miami Freakhosting Connection to 104.168.74.XX:80 failed
    Colombia, Barranquilla NetActuate Connection to 104.168.74.XX:80 failed
    Canada, ON, Toronto NetActuate Connection to 104.168.74.XX:80 failed
    USA, NY, Buffalo ColoCrossing Connection to 104.168.74.XX:80 failed
    USA, NY, Buffalo Evolushost Connection to 104.168.74.XX:80 failed
    USA, VA, Ashburn NetActuate Connection to 104.168.74.XX:80 failed
    USA, VA, Ashburn Freakhosting Connection to 104.168.74.XX:80 failed
    USA, NJ, Secaucus Goodleaf Connection to 104.168.74.XX:80 failed
    USA, NJ, Secaucus Interserver Connection to 104.168.74.XX:80 failed
    USA, NY, New York Hurricane Connection to 104.168.74.XX:80 failed
    USA, NY, New York Teracast Connection to 104.168.74.XX:80 failed
    Canada, QC, Montreal OVH Connection to 104.168.74.XX:80 failed
    Chile, Santiago NetActuate Connection to 104.168.74.XX:80 failed
    Argentina, Buenos Aires Advantun Connection to 104.168.74.XX:80 failed
    Paraguay, C.D.E. ASISPY Connection to 104.168.74.XX:80 failed
    Brazil, Sao Paulo NetActuate Connection to 104.168.74.XX:80 failed
    Brazil, Sao Paulo HyperFilter Connection to 104.168.74.XX:80 failed
    Brazil, Barueri Migo Internet Connection to 104.168.74.XX:80 failed
    Brazil, Fortaleza AlCloud Connection to 104.168.74.XX:80 failed
    Morocco, Fez Hostoweb Connection to 104.168.74.XX:80 failed
    Spain, Madrid NetActuate Connection to 104.168.74.XX:80 failed
    Spain, Barcelona Cubepath Connection to 104.168.74.XX:80 failed
    UK, Manchester NetActuate Connection to 104.168.74.XX:80 failed
    UK, Newcastle FyfeWeb Connection to 104.168.74.XX:80 failed
    UK, Slough Virtuo Connection to 104.168.74.XX:80 failed
    UK, London Cosmic Global Connection to 104.168.74.XX:80 failed
    UK, London Evolushost Connection to 104.168.74.XX:80 failed
    UK, London Freakhosting Connection to 104.168.74.XX:80 failed
    Ghana, Accra NetActuate Connection to 104.168.74.XX:80 failed
    South Africa, Johannesburg EdgeNext Connection to 104.168.74.XX:80 failed
    France, Rennes Vyme Connection to 104.168.74.XX:80 failed
    France, Paris Online.net Connection to 104.168.74.XX:80 failed
    France, Paris NetActuate Connection to 104.168.74.XX:80 failed
    Netherlands, Amsterdam Online.net Connection to 104.168.74.XX:80 failed
    Netherlands, Amsterdam Hybula Connection to 104.168.74.XX:80 failed
    Netherlands, Amsterdam Interhost Connection to 104.168.74.XX:80 failed
    Netherlands, Amsterdam Nexonhost Connection to 104.168.74.XX:80 failed
    Netherlands, Eygelshoven Evolushost Connection to 104.168.74.XX:80 failed
    Netherlands, Eygelshoven MLNL.HOST Connection to 104.168.74.XX:80 failed
    Netherlands, Eindhoven YottaSrc Connection to 104.168.74.XX:80 failed
    Nigeria, Lagos EdgeNext Connection to 104.168.74.XX:80 failed
    Norway, Sandefjord Gigahost Connection to 104.168.74.XX:80 failed
    Switzerland, Zurich iFog Connection to 104.168.74.XX:80 failed
    Switzerland, Zurich Private Layer Connection to 104.168.74.XX:80 failed
    Germany, Frankfurt ZetNet Connection to 104.168.74.XX:80 failed
    Germany, Frankfurt Nexonhost Connection to 104.168.74.XX:80 failed
    Germany, Frankfurt Freakhosting Connection to 104.168.74.XX:80 failed
    Germany, Nuremberg NetActuate Connection to 104.168.74.XX:80 failed
    Germany, Berlin Evolushost Connection to 104.168.74.XX:80 failed
    Slovenia, Maribor PipeHost Connection to 104.168.74.XX:80 failed
    Austria, Vienna PipeHost Connection to 104.168.74.XX:80 failed
    Austria, Vienna Evolushost Connection to 104.168.74.XX:80 failed
    Sweden, Stockholm Skhron Connection to 104.168.74.XX:80 failed
    Poland, Warsaw H2.Nexus Connection to 104.168.74.XX:80 failed
    Poland, Wyszkow Freakhosting Connection to 104.168.74.XX:80 failed
    Kosovo, Prishtine RS Computers Connection to 104.168.74.XX:80 failed
    Bulgaria, Sofia 7DC Connection to 104.168.74.XX:80 failed
    Greece, Athens Fusioned Connection to 104.168.74.XX:80 failed
    Finland, Helsinki H2.Nexus Connection to 104.168.74.XX:80 failed
    Romania, Bucharest ZetNet Connection to 104.168.74.XX:80 failed
    Romania, Bucharest Nexonhost Connection to 104.168.74.XX:80 failed
    Romania, Bacau Freakhosting Connection to 104.168.74.XX:80 failed
    Kyiv, Ukraine Lifecell Connection to 104.168.74.XX:80 successful – 2.09 ms
    Turkey, Izmir Netdirekt Connection to 104.168.74.XX:80 failed
    Turkey, Istanbul Oneprovider Connection to 104.168.74.XX:80 failed
    Turkey, Istanbul Teknosos Connection to 104.168.74.XX:80 failed
    Turkey, Istanbul YottaSrc Connection to 104.168.74.XX:80 failed
    Turkey, Istanbul Netlen Connection to 104.168.74.XX:80 failed
    Turkey, Bursa NetWeb Connection to 104.168.74.XX:80 failed
    Turkey, Ankara Upcell Connection to 104.168.74.XX:80 failed
    Turkey, Ankara 3C1B Connection to 104.168.74.XX:80 failed
    Cyprus, Limassol CL8 Connection to 104.168.74.XX:80 failed
    Israel, Tel Aviv Oneprovider Connection to 104.168.74.XX:80 failed
    Israel, Tel Aviv Interhost Connection to 104.168.74.XX:80 failed
    Kenya, Nairobi NetActuate Connection to 104.168.74.XX:80 failed
    UAE, Dubai NetActuate Connection to 104.168.74.XX:80 failed
    UAE, Dubai Serverwala Connection to 104.168.74.XX:80 failed
    Oman, Muscat EdgeNext Connection to 104.168.74.XX:80 failed
    Iran, Tabriz ArvanCloud Connection to 104.168.74.XX:80 failed
    Iran, Tehran ArvanCloud Connection to 104.168.74.XX:80 failed
    Azerbaijan, Baku EdgeNext Connection to 104.168.74.XX:80 failed
    Pakistan, Karachi EdgeNext Connection to 104.168.74.XX:80 failed
    India, Mumbai Vultr Connection to 104.168.74.XX:80 failed
    India, Noida YottaSrc Connection to 104.168.74.XX:80 failed
    India, Bengaluru Digital Ocean Connection to 104.168.74.XX:80 failed
    India, Bengaluru Serverwala Connection to 104.168.74.XX:80 failed
    India, Chennai NetActuate Connection to 104.168.74.XX:80 failed
    Bangladesh, Jessore Race Online Connection to 104.168.74.XX:80 failed
    Bangladesh, Dhaka Dot Internet Connection to 104.168.74.XX:80 failed
    Bangladesh, Dhaka BTCL Connection to 104.168.74.XX:80 failed
    Bangladesh, Dhaka Hello Tech Connection to 104.168.74.XX:80 failed
    Bangladesh, Dhaka Mango Connection to 104.168.74.XX:80 failed
    Bangladesh, Dhaka Layer3 Connection to 104.168.74.XX:80 failed
    Bangladesh, Dhaka STT Startrek Connection to 104.168.74.XX:80 failed
    Bangladesh, Dhaka Link3 Connection to 104.168.74.XX:80 failed
    Bangladesh, Dhaka Race Online Connection to 104.168.74.XX:80 failed
    Bangladesh, Dhaka Grameen Connection to 104.168.74.XX:80 failed
    Bangladesh, Dhaka Sam Online Connection to 104.168.74.XX:80 failed
    Bangladesh, Dhaka Carnival Connection to 104.168.74.XX:80 failed
    Bangladesh, Cumilla CCTV Online Connection to 104.168.74.XX:80 failed
    Bangladesh, Chittagong Race Online Connection to 104.168.74.XX:80 failed
    Thailand, Bangkok SG.GS Connection to 104.168.74.XX:80 failed
    Thailand, Bangkok Bangmod Connection to 104.168.74.XX:80 failed
    Singapore SG.GS Connection to 104.168.74.XX:80 failed
    Singapore NetActuate Connection to 104.168.74.XX:80 failed
    Indonesia, Bogor Pakuan Univer Connection to 104.168.74.XX:80 failed
    Indonesia, Jakarta Atharva Connection to 104.168.74.XX:80 failed
    Hong Kong MLNL.HOST Connection to 104.168.74.XX:80 failed
    Hong Kong NetActuate Connection to 104.168.74.XX:80 failed
    Hong Kong Backwaves Connection to 104.168.74.XX:80 failed
    Japan, Tokyo DODO Connection to 104.168.74.XX:80 failed
    Japan, Tokyo Vultr Connection to 104.168.74.XX:80 failed
    Japan, Tokyo NetActuate Connection to 104.168.74.XX:80 failed
    Japan, Tokyo Backwaves Connection to 104.168.74.XX:80 failed
    Australia, Sydney Vultr Connection to 104.168.74.XX:80 failed
    Australia, Sydney NetActuate Connection to 104.168.74.XX:80 failed
    Mongolia, Ulaanbaatar EdgeNext Connection to 104.168.74.XX:80 failed
    Taiwan, Taichung Google Connection to 104.168.74.XX:80 failed
    China, Chengdu Tencent Connection to 104.168.74.XX:80 failed
    China, Chongqing Tencent Connection to 104.168.74.XX:80 failed
    China, Guangzhou Tencent Connection to 104.168.74.XX:80 failed
    China, Nanjing Tencent Connection to 104.168.74.XX:80 failed
    China, Jiangsu China Telecom Connection to 104.168.74.XX:80 failed
    China, Jiangsu China Mobile Connection to 104.168.74.XX:80 failed
    China, Lishui China Telecom Connection to 104.168.74.XX:80 failed
    China, Lishui China Unicom Connection to 104.168.74.XX:80 failed
    China, Lishui China Mobile Connection to 104.168.74.XX:80 failed
    China, Qingdao Aliyun Connection to 104.168.74.XX:80 failed
    China, Shanghai Aliyun Connection to 104.168.74.XX:80 failed
    China, Shanghai Tencent Connection to 104.168.74.XX:80 failed
    
    
    
    So interesting with Kyiv, Ukraine

  • totally_not_bannedtotally_not_banned Member
    edited June 9

    Have you tried resetting your router? Like turning it off and on again?

  • wisepandawisepanda Member

  • totally_not_bannedtotally_not_banned Member

    Why are you running ssh on port 80?

    Thanked by 6oloke tentor Scioner Saragoldfarb enclose khalequzzaman
  • deafcondeafcon Member

    DaddyRock moved your node to Ukraine? That's pretty cool. FYI, my storage server is up. A transfer I've been running has slowed to a crawl, but that could be rate limiting on either the DediRock side or the origin side, not an indication of a real problem.

  • wisepandawisepanda Member

    @totally_not_banned said:
    Why are you running ssh on port 80?

    It's a test by the website https://tcp.ping.pe/
    I don't know why, and you asked me , who should I ask? :p :p :p :p :p

  • wisepandawisepanda Member

    @deafcon said:
    DaddyRock moved your node to Ukraine? That's pretty cool.......

    If they do this, I have no objections. On the contrary, I find it very exciting

  • ehabehab Veteran

    Thanked by 7s0n1c totally_not_banned Saragoldfarb CheepCluck khalequzzaman stable_genius dsbnoob
  • wisepandawisepanda Member

    @totally_not_banned said:
    Have you tried resetting your router? Like turning it off and on again?

    You mean , it's the problem of my network connection?
    I don't agree with u sir.
    I am running other network programs at the same time and they are all functioning normally

  • totally_not_bannedtotally_not_banned Member

    @wisepanda said:

    @totally_not_banned said:
    Why are you running ssh on port 80?

    It's a test by the website https://tcp.ping.pe/

    Cool. Testing is always good no matter what. When in doubt test, test, test and then test again. If that still doesn't help turn the fridge to -30°C.

    I don't know why, and you asked me , who should I ask? :p :p :p :p :p

    That'll be $7 for the cerebral hemorrhage.

    Thanked by 2wisepanda khalequzzaman
  • DediRockDediRock Member, Patron Provider

    @wisepanda said:
    @DediRock

    Hello @wisepanda,

    Sorry for the trouble here, my guys are checking this now.

    DediRock Makes It Right™

    Thanked by 1wisepanda
  • MainfrezzerMainfrezzer Member

    This is quite comical, I like it

  • totally_not_bannedtotally_not_banned Member

    @DediRock said:
    Sorry for the trouble here, my guys are checking this now.

    What setting is your fridge at?

  • lovelyserverlovelyserver Member

    @wisepanda said:

    No need for that :80

    Test just the IP. It should be fine.

    Thanked by 1wisepanda
  • wisepandawisepanda Member

    @lovelyserver said:

    @wisepanda said:

    No need for that :80

    Test just the IP. It should be fine.

    ok.
    But I also installed nginx.

  • dbadudedbadude Member

    @wisepanda dont ping to a port remove :80 Panda should ping to a IP.
    Use telnet to a port to check its open or not.
    telnet IPADDRESS SSH-PORT
    telnet 104.168.74.xxx 22
    quit

    Thanked by 1raindog308
  • totally_not_bannedtotally_not_banned Member

    @dbadude said:
    Use telnet to a port to check its open or not.

    Personally i prefer nc -v [ip] [port] but in the end it doesn't make much of a difference i guess.

  • PuDLeZPuDLeZ Member

    @totally_not_banned said:

    @dbadude said:
    Use telnet to a port to check its open or not.

    Personally i prefer nc -v [ip] [port] but in the end it doesn't make much of a difference i guess.

    same here (prefer netcat) but in this situation, they're basically the same thing

  • lowendclientlowendclient Member

    Try reboot or VNC first.

  • DrNutellaDrNutella Member
    edited June 10

    Why didn’t you open ticket and go away?
    @DediRock support is very good

    Thanked by 1nghialele
  • CheepCluckCheepCluck Member

    @DrNutella said:
    Why didn’t you open ticket and go away?
    @DediRock support is very good

    Thread first, work order second.

    Thanked by 3nghialele totally_not_banned gbzret4d
  • s0n1cs0n1c Member

    @DrNutella said:
    Why didn’t you open ticket and go away?
    @DediRock support is very good

    lowendsupport 2 minute response time better than 20 hour response time from dedirock support

    Thanked by 4stablecloud oloke khalequzzaman tototo
  • stablecloudstablecloud Member, Patron Provider

    Let me check my crystal ball.

    Have you tried contacting dedirock?> @s0n1c said:

    @DrNutella said:
    Why didn’t you open ticket and go away?
    @DediRock support is very good

    lowendsupport 2 minute response time better than 20 hour response time from dedirock support

    I try my best :)

    Thanked by 3oloke khalequzzaman s0n1c
  • dbadudedbadude Member

    a 10 dollar host and complaining about long 20 hour respond times, only on lowend. priceless :D

  • LeviLevi Veteran

    Please paste your private key here. We will do whatever we can.

    Thanked by 6khalequzzaman totally_not_banned rpqu gbzret4d Nekopara wisepanda
  • dbadudedbadude Member

    @Levi said:
    Please paste your private key here. We will do whatever we can.

    Social hacking detected...

    Thanked by 1khalequzzaman
  • zedzed Veteran

    Oh gosh™

    Thanked by 1ehab
Sign In or Register to comment.