Situation
I completed the OpenEMR Cloud Express on AWS.
Everything seemed to go fine and I have an instance running.
I received the Public, private, IP and DNS information.
When I try to connect the the IP I get an error saying:
“There was a problem connecting to your instance”
When I try ssh to connect, it times out without connecting.
On the EC2 console it shows the instace state as running.
OpenEMR Version
I assume the version is 6.0.
Did I misunderstand it would be auto installed with this?
Browser:
Tired Chrome and Edge
Operating System
Windows 10 Pro
Logs
Did you check the logs?
Can not start OpenEMR to check logs
Try SSH’ing but add -v to generate some more info about the issue. Also, check your network settings in AWS to ensure your security group is allowing inbound traffic on ports 80 (HTTP), 443 (HTTPS), and 22 (SSH)
I suspect this isn’t a security group issue, because if it was security groups it’d be responding on 80/443 – this is a networking issue, the instance either has no public IP or it’s in a VPC subnet that can’t route to the world.
Thanks for the suggestions.
I tried the -v and it still timed out.
I have also tried a different internet connection (on my pc)
Still same timed out.
I tried to attach and image but could not.
Here is the ssh reply
OpenSSH_for_Windows
debug1: Connecting to 3.145.81.119 [3.145.81.119] port 22
debug1: conect to address 3.145.81.119 port 22: Connection timed out
ssh: connect to host 3.145.81.119 port 22 Connection timed out
On the EC2 console what does it show for your public ip? Did you use the default Virtual Private Cloud (VPC) settings for the network to launch express?
There’s not a lot to go on, unfortunately. We just got finished serving a ticket on the main repo where a user on Windows was unable to connect to EC2 instances (not ours alone) for completely unclear reasons, so I know it can happen if not why.
Note that it’s not really possible for any of the Amazon packages to fail in such a way that ssh will be non-responsive, that’s just flat not going to happen and it’s pointing to problems with the network or security groups. I recommend trying to start a regular old Amazon instance in the same VPC and subnet and see if you can connect to that.
If you can’t, you know you’ve got a different problem to resolve that. If you can, then you’ve got something to compare now.
I did not have any issues setting up OpenEMR on my local workstation.
Why AWS would not work was something I did not feel was worth the effort to spend more time on. I followed all of the guides and suggestions to make it work but the problem persisted.
I ended up creating a web portal (static public IP address) and installed OpenEMR on my server. It worked first time and has not had any issues. It was actually very easy to do and inexpensive.
Unfortunately, I have not been able to complete the setup of OpenEMR to be used in my company. (My company has other projects I’ve been busy doing.)
When I check OpenEMR, it works fine but we have not put any data into the system and start using it as an EMR system.
We will probably need to hire a consultant / developer to assist in implementation of OpenEMR in my company. I’m sure the expense of that will be worth the cost.
I seem to be able to SSH in on the free Lightsail version but even trying to SSH in on the Express version is timing out. I’m seeing these errors so trying to work through these - I’m on a Mac so not sure I can do the first but trying to set up the IAM instance profile.
You wouldn’t be able to connect that way, I never installed SSM Agent. (Maybe I should?)
I will note that the user you should connect with is “ubuntu”, not “root”, though that wouldn’t cause timeouts. I continue to suspect this is a network or security group issue – no other user has reported an inability to connect to an Express instance. The domain and command do look otherwise correct, however.
For the security group, I just chose the default security group settings. It seems to be passing both of the status checks. The only other thing I can think of is that Im currently located in the west coast but the instance is on east coast availability zone, would that make a difference? Also where would I have set up the ubuntu user?
You wouldn’t’ve set it up, I did when I made the instance. I gave AWS a Ubuntu 20.04 instance I configured, and then when you spun it up in your environment AWS added your key to it.
But I think you just put your finger on the problem – the “default” security group does not allow public access to servers. Create a new security group that allows inbound access to 80/443 and your ip to 22 and add it to the instance and you should be good.
(Do not /replace/ the ‘default’ security group, that’s important and it matters, just add your new group.)
| 
