Submitted by bizmate on Mon, 07/05/2010 - 11:21
Hi
I have started an instance of the Virtualmin Amazon AMI ami-dc1a32a8 and as soon as i started and opened ports for it I got this error when I point to port 10000
http://ec2-79-125-39-63.eu-west-1.compute.amazonaws.com:10000/
Error - Bad Request
This web server is running in SSL mode. Try the URL https://10.227.197.220:10000/ instead.
The instance is down now. I did run an updated through SSH but that did not make any difference.
Could you please suggest what I can do to fix this? Is this a bug or misconfiguration? Sounds strange that it does not work from the start
Thanks
Diego
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Mon, 07/05/2010 - 11:46 Comment #1
The URL you should use is https://ec2-79-125-39-63.eu-west-1.compute.amazonaws.com:10000/
Unfortunately due to EC2's network address translation, virtualmin doesn't know the systems external IP address, so the URL it suggests you use is incorrect.
Submitted by bizmate on Tue, 07/06/2010 - 04:19 Comment #2
Hi Jamie
thanks for your reply. Wha t you wrote makes perfect sense. When using the HTTPS
https://ec2-79-125-89-248.eu-west-1.compute.amazonaws.com:10000/
I get a standard page from the server
Going back to my original intention, I wanted to follow the instructions on
https://www.virtualmin.com/documentation/aws/virtualmin_gpl_ami
to get started with the webmin to set up all the server related aspects
As you can see in the tutorial it suggests I should point to http rather than https. Do you know where is webmin running in the current version of the AMI?
Thanks
Diego
Submitted by bizmate on Tue, 07/06/2010 - 05:45 Comment #3
Hi
never mind my last post. There is a proxy problem on my side that stops traffic through 1000 on HTTPS.
Thanks for your time
Submitted by JamieCameron on Tue, 07/06/2010 - 11:59 Comment #4
Thanks for pointing that out - the docs are indeed wrong, and should use the https URL. I have fixed that now.
Submitted by Issues on Tue, 07/20/2010 - 14:19 Comment #5
Automatically closed -- issue fixed for 2 weeks with no activity.