Can't login to ligthsail via browser SSH

0

Suddenly I can't login via Browser SSH from AWS console to my Joomla ligthsail instance. Get error UPSTREAM_NOT_FOUND [519] .

I have also tried to create an new instance from an snapshot that have worked w/o problem but Now I get the same error

What can I do?

Regards Digiloo

digiloo
질문됨 7달 전203회 조회
3개 답변
0

Good afternoon, You cant try use aws ssm from command line in your's workstation, not from browser or if you have ssh key - try to connection via this way.

Commnad line for aws ssm: aws ssm start-session --target i-xxxxxxxxxxx --profile default

답변함 7달 전
  • Ok Thank you I will try later but for your knowledge I can't no longer login from my Mac with my ssh keys and not from another AWS instance

  • Will this command give me an interactive bash shell as SSH? But does anyone know why SSH suddenly don't work any more for any dispite of creating a new Lightsail instance from a earlier fully working snapshot?

0

Good afternoon,

Will this command give me an interactive bash shell as SSH?

It's only work for AWS, not for Lightsail

Try to generate the new SSH key and upload to instance via Lightsail UI

https://lightsail.aws.amazon.com/ls/docs/en_us/articles/understanding-ssh-in-amazon-lightsail

https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-remove-ssh-key-on-instance

답변함 7달 전
  • Thank you , but id doesn't seem to be a certificate problem OpenSSH_8.6p1, LibreSSL 3.3.6 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/* matched no files debug1: /etc/ssh/ssh_config line 54: Applying options for * debug2: resolve_canonicalize: hostname 18.197.133.62 is address debug3: expanded UserKnownHostsFile '/.ssh/known_hosts' -> '/Users/hakan/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '/.ssh/known_hosts2' -> '/Users/hakan/.ssh/known_hosts2' debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling debug3: ssh_connect_direct: entering debug1: Connecting to 18.197.133.62 [18.197.133.62] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x48 debug1: connect to address 18.197.133.62 port 22: Connection refused ssh: connect to host 18.197.133.62 port 22: Connection refused

    / Hakan

0

And if I didn't mentioned before the problem is account wide . Creating a new instance didn't work.

/ Hakan

digiloo
답변함 7달 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠