You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some users reported that the Apache start/license page is not loading after the first booting of the Bayesforge AIM.
If you canot load the Bayesforge start page you need to log into the image via ssh e.g. on OSX or Linux you'd issue a command like this:
sh -i .aws/west1.pem ubuntu@ec2-54-152-181-32.compute-1.amazonaws.com
where .aws/west1.pem needs to be replaced with the path to your private ssh key and ec2-54-152-181-32.compute-1.amazonaws.com with your EC2 instances public IP address. I.e.
`sh -i ubuntu@
Amazon describes who to connect with Windows using the freeware Putty at this link.
Once you logged into your EC2 session issue the following commands:
You can check that the Apache web sever was started with:
sudo systemctl status apache2
You should now be able to display the Bayesforge launch page when pointing your browser to you instance's public IP such as http://ec2-54-152-181-32.compute-1.amazonaws.com and follow the instructions to log into your private Bayesforge Jupyter server.
The text was updated successfully, but these errors were encountered:
Some users reported that the Apache start/license page is not loading after the first booting of the Bayesforge AIM.
If you canot load the Bayesforge start page you need to log into the image via ssh e.g. on OSX or Linux you'd issue a command like this:
sh -i .aws/west1.pem ubuntu@ec2-54-152-181-32.compute-1.amazonaws.com
where .aws/west1.pem needs to be replaced with the path to your private ssh key and ec2-54-152-181-32.compute-1.amazonaws.com with your EC2 instances public IP address. I.e.
`sh -i ubuntu@
Amazon describes who to connect with Windows using the freeware Putty at this link.
Once you logged into your EC2 session issue the following commands:
sudo systemctl enable apache2
sudo systemctl start apache2
You can check that the Apache web sever was started with:
sudo systemctl status apache2
You should now be able to display the Bayesforge launch page when pointing your browser to you instance's public IP such as http://ec2-54-152-181-32.compute-1.amazonaws.com and follow the instructions to log into your private Bayesforge Jupyter server.
The text was updated successfully, but these errors were encountered: