OTOY Forums

Hi all,

At long last I got an instance of the Cloud Workstation AMI responding via RDP (the AMI ID is
AMI-OTOY-OCTANE-WINDOWS_1.0-1765694b-3372-4e71-9d75-0703468ad20d-ami-8f5d16e6.1). But when I connect to the Otoy bouncer service/Javascript loader at

http://aws.otoy.com/?connect=//[IP]:8090/?NOCRYPTO=1%CD%BESTATUS=1%CD%BEAUTOLOCK=0%CD%BEWAN=12%CD%BEGUID=[GUID]

it appears to timeout while making the WebSocket connection.

What gives? How do I fix this? And do I get refunded for these issues?

Please PM me the IP address of your AMI and I will help you debug it. One thing I noticed in the connection string above is that all the ";" are escaped with "%CD%BE".

make sure the URL is in this form when you enter it in the browser:

http://aws.otoy.com/?connect=//[IP]:8090/?NOCRYPTO=1;STATUS=1;AUTOLOCK=0;WAN=12;GUID=[GUID]

We have private AMIs - same as the ones in the marketplace. If we can't get this resolved quickly, we'll get you a free hour on one of those.

PM sent.

I am having this same issue have sent you a PM

I am having the same issue?

http://aws.otoy.com/?connect=//IP:8090/ ... ATION=3364

returns a timeout error

Hello,

I have the exact same problem with my newly created server.
It seems to connect to the websocket on port 443, but then the timeout box appears..

Perhaps it's a firewall problem? Although I've allowed all ip traffic towards that IP from our IP,so it really shouldn't be the problem.

I am having the same problem. I created a octane desktop with autodesk and I can connect via RDP to access the instance and retrieved the guid. I have tried using both the public DNS and have attached an elastic IP.

http://aws.otoy.com/?connect=//<ip>:8090/?NOCRYPTO=1;STATUS=1;%20AUTOLOCK=0;WAN=12;GUID=<guid>

the screen is blank and eventually gets a timeout error. there's nothing in the logs on the windows instance.

Having the same issues here, checked GUID and IP address, not sure what's going on. I'm using the Autodesk AMI.

Can you confirm if the security group policy was copied over from the product load form?

I am also going to turn off the GUID check for all instances sent to me over PM (you will need to restart them).

For anyone doing first time testing of the AMIs - the best one to load is the ADSK AMI as it is ready and set up.

Thank you.

I'm experiencing much the same issues. I've placed the GUID=etc in the User Data per the documentation and am using the following link to get at my running instance:

http://aws.otoy.com/?connect=//<instance>.compute-1.amazonaws.com:8090/?NOCRYPTO=1;STATUS=1;
AUTOLOCK=0;WAN=12;GUID=<GUID>

I have yet to be able to successfully attach to the system outside of RDP.