Before I'd traveled for 3 weeks, my connection to EC2 windows - ec2-54-186-219-106.us-west-2.compute.amazonaws.com - was perfect. In this period, I was away, on vacation, and didn't connect to it. Now, I try to connect via RDP from my MacBook and see the message:"Remote Desktop can't connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network". I've checked some forums and got some advice like: reboot my instance, change my security group, add port 80 to my security group, but nothing works. Any idea?
This is how I solve my problem: I've attached an IP to my instance, and it starts working again. I hope it helps someone who is facing a similar situation. That's all folks!
Related
I have an older dedicated PC running on my home network as a webserver. Trying to retire it by replacing it with a VM on a brand new workstation Santa brought me. Simple home hobbyist network consists of router, 10Gb switch and of course computing devices off of that.
The new machine is running Windows11 Pro, and via Hyper-V I have a CentOS 7 VM. I've configured the firewall to enable http service (and port 80) being accessible from outside my network. I'm running httpd. From behind my router/switch I can access the web server with no problem, from the host machine and other machines on my network). Alas - I'm unable to access this web server remotely/externally - even after turning of the VM's firewall and ensuring port forwarding was properly pointing to IP:80 from my router. I have been scouring the web/forums/etc. for days now - nothing I've tried seems to work.
Also, I was careful in ensuring the Hyper-V settings for a virtual switch are pointing to my actual hardware NIC and set accordingly as found here and other forums (see attached image for details).
From all the "experimentations" I've tried - it's seems like the port is just not being forwarded from my router properly. So it's really pointing towards my router at this point. BUT - I can and have configured real hardware before (over decades) with no problem. Since I'm NEWB to Hyper-V and VM's - I'm worried some setting may not be correct.
Thus - reaching out to anyone with similar experience who's solved this problem. Thanks in advance.
Here's a graphic in which I captured some of the many things I've tried to no avail.
settings, etc.
When using RDP to connect to my Azure Windows Server 2016 VM, I am able to connect and the blue loading screen appears briefly then turn black and the connection is broken. I have worked through all the troubleshoot suggestions of:
After each troubleshooting step, try reconnecting to the VM:
1) Reset Remote Desktop configuration.
2) Check Network Security Group rules / Cloud Services endpoints.
3) Review VM console logs.
4) Reset the NIC for the VM.
5) Check the VM Resource Health.
6) Reset your VM password.
7) Restart your VM.
8) Redeploy your VM.
But nothing has worked.
Any suggestions greatly appreciated.
According to your description. Many possible reasons may cause this black screen. Firstly You can try to upsize the VM via the Azure portal.
Also, I suggest checking the RDP client side.
Use control+alt+end, then sign out to close the RDP session and launch another one.
try to connect through Remote Desktop Manager which can resolve the same issue for someone.
Known issue: A black screen may appear while logon by using remote desktop
From Virtual Machine settings on the portal, find Diagnose and solve problems, follow the steps of SOLUTIONS TO COMMON PROBLEMS.
More references about Black Screen after RDP
I've been running tomcat on my Amazon EC2 instance for a few weeks just fine but all of a sudden, I became unable to connect to it. When I use putty I can connect to it fine but when I try to connect with my browser by using ip:8080 , I can't connect anymore. I've tried restarting the instance (and of course, adjusting my input ip accordingly), restarting the tomcat server within the instance, and checking the security groups. Nothing seems to work. I have no idea why it stopped working out of the blue. How should I proceed?
There are many reasons to why you cannot connect. The best way to solve this is to follow Amazons troubleshooting tips, found here.
I had the same issue. The amazon troubleshooting did not help. Then I remembered that I ad a line in my system32/driver/etc host file when I did some site migration.
Deleted that line and I was back in business again.
Hope that helped
I have an aws ec2 micro (free tier, so no tech support) and as is expected, when I got back in the morning my PuTTY had timed out from being connected for a few hours, this has happened multiple times before. When I went to restart the connection, I got a connection refusal. Tried more times, nothing. WinSCP, what I use for file transfer, also can't connect to a new login, but praise the lord allowed me to download all the files I had on the server. I tried on another device and through telnet on all the open incoming ports, connections refused. The MindTerm or whatever it's called when you click connect (on firefox) also couldn't connect.
The instance is all green, volume is all green, passing all status checks as well.
I have looked at other threads, but they are for after a restart or changing of the ssh config. I haven't touched anything. I doubt the permissions or anything have been compromised.
Apparently just hitting reboot on the server did it. Can't believe I didn't think of something so easy.
I've been running an instance EC2 through Laravel forge for about 2000 hours and this morning got this error while trying to reach it:
SQLSTATE[08006] [7] could not connect to server: Connection refused Is
the server running on host "172...***" and accepting TCP/IP
connections on port 5432?
After SSHing into the server I've getting a similar error when trying to run a command. I've dug through AWS but don't see any errors being throw. I double checked the ip address for the instance to make sure the IP hadn't changed for any reason. Of course I'm a little behind on my backups for the application so I'm hoping someone might have some ideas why else I can do to try and access this data. I haven't made any changes to the app in about 10 days, but found the error while I was pushing an update. I have six other instances of the same app that weren't affected (thankfully) but makes me even more confused with the cause of the issue.
In case anyone comes across a similar issue, here's what had happened. I had an error running in the background which had filled up the EC2 harddrive's log. Since the default Larvel/Forge image has a DB running within in the EC2 instance, once it ran out of room everything stopped working. I was able to SSH in and delete the log though, and everything started working again.
To prevent the issue from happening again I then created an amazon RDS and used that rather than the EC2 instance. It's about three or four times the price of just an EC2 instance, but still not that much and the confidence I now have in the system is well worth it.