Questions tagged with Compute
Content language: English
Sort by most recent
We have setup remote apps to be used via RDP on a Windows Server. Users have reported that they will get disconnected mid-session. They are usually logged in all day. We haven't been able to find a cause.
We have done the following:
1. Increased the server hardware based on AWS provisioning suggestion
2. Set up Domain and Local GPO to keep instances active, auto reconnect sessions, and only allow one session per user
3. Checked the Remote Desktop App settings to ensure we don't have a timeout issue there
4. Checked Event Logs both on the server and at the AD controller (No errors)
5. Checked security settings for anything potential connected to remote desktop
6. Made sure we have remote desktop licenses installed
We are running the Apps over a VPN and each server is setup to serve as a RD broker as well as host the RD App.
Any ideas?
Hello,
Today I attempted an instance type change on a Windows machine from m5.4xlarge to c6a.4xlarge resulting in Instance reachability check failed. I've tried rebooting, stopping, and starting the instance, but the outcome was the same: no connectivity.
Are there any networking differences between the 2 instance types that would require driver installation? I'm asking about the network, as the instance screenshot displayed no connectivity on the network adapter and the remote desktop connection was not working either.
One of our EC2 windows (Windows 2022 Data Center Edition) instance randomly stops without any manual interference.
It's a **c6a.8xlarge** instance type running at **Mumbai location**. The server is used for RDP purpose. Whenever users complain they are kicked out of their sessions, we mostly see that it is in "Stopped" mode in the dashboard.
This is really impacting our production.
How do we resolve this issue?
I created a new Ubuntu 22.02 LTS instance two days ago. Instance type T2.Medium.
Every night at about 08:20 UTC I get an error message in the log 'eth0 Could not set route: Connection Timed Out'. up until this point my log is full of standard docker messages about mounts being deactivated and the application is running fine.
All normal messages have stopped, docker isn't deactivating various runc.* mounts up until this point. once that eth0 could not set route message appears the runc messages stop
after that the instance is unreachable and fails the instance checks, I am unable to stop it gracefully. Once it is force stopped, and restarted then it was fine again, until that time the next day when network connectivity is lost. This has happened two days in a row.
There is no indication in the syslog except that eth0 timed out, and fails. I've had machines ssh'd into it and they get disconnected.
Hello,
Does the time window for calculating the money spent in the **Savings Plans** always **start at the full hour** (e.g. at 13:00, 14:00, 15:00 etc. and NOT e.g. at 13:05, 14:05, 15:05 etc.)?
According to the chart in Cost Explorer (with hourly granularity enabled) this is the case, but I didn't find it explicitly mentioned in the documentation.
I created a public instance and tried to connect to it through putty but when I tried to SSH to it from PUTTY with proper IP address and .ppk KEY along with correct USER ID, server responded as -
" Server refused our key " and " No supported authentication methods available (server sent: publickey,gssapi-keyex,gssapi-with-mic) "
how do I resolve this error?
Instance configuration
- AMI : Amazon Linux
- I can HTTP to the instance through browsers and it's working
- used Putty terminal emulator
- KEY is Generated from EC2
- I set Private key in Connection\Auth\Credentials in putty.
- I confirmed the user name using which is ec2-user for my instance AMI.
-
when I googled I found this but I couldn't understand -
https://aws.amazon.com/premiumsupport/knowledge-center/ec2-server-refused-our-key/
I hope someone will give me a little explanation
Hello Team,
For the AMI ID ami-02f3f602d23f1659d (al2023-ami-2023.0.20230315.0-kernel-6.1-x86_64), I am seeing that crontab is missing
[root@ip-172-31-11-172 ~]# contab -l
-bash: contab: command not found
After that I have installed the crontab manually using the command **yum install cronie cronie-anacron**
But could you please let me know, Is the AWS missed to include crontab or hereafter the AMI will come up without crontab. Could you please confirm.
I have 2 ec 2 instances running and am able to login to both from pc desktop but not from Android mobile
It is my understanding that we can have 2 connections through rdp, is these connections to the server or the instances, so my question is my having 2 instances is that my connections used up and I need to pay for rdp licence then?
Or should I be able to connect through my mobile as well?
If it is possible to connect through mobile, can someone detail the process for doing so?
If I need to buy licences, where do I find details to do that and also associated costs, I would need a connection to each instance through mobile, so is that 2 rdp licenses required?
any pointers appreciated
Many Thanks
Gordon
I have a WordPress site on LightSail. Tried to login but can't navigate to wp-admin. Tried to login to Plesk and it says the disk is full. How do I get into the account to free up space?
ubuntu@thirsty-kalam:~$ sudo plesk login
DB query failed: SQLSTATE[HY000]: General error: 1021 Disk full (/tmp/#sql_301_0.MAI); wai
ting for someone to free some space... (errno: 28 "No space left on device"), query was: D
ESCRIBE `clients`
When I was trying to connect to instances i can't able to connect to it ,it shows me an error network error : connection timed out
I'm running a drill on servers that are using the same configuration in DRS. One of the servers fails with the Error: Failed to connect using HTTP channel. The other servers failover as expected. All servers are using the default security group created by DRS. The launch templates are similar, same subnet, etc. How can I troubleshoot the HTTP error?
I am unable to connect to server to server using ssh.
the error message is ubuntu@ip-60-0-0-48:~$ ssh root@40.0.6.136
ssh: connect to host 40.0.6.136 port 22: Connection timed out
ubuntu@ip-60-0-0-48:~$