OTOY Forums

i feel a lil dumb but i can log the plug in.
after i resolved some problems with my internet connection in general, i went back to daz and the plug in is asking me to be activated.
i've tried using my user name & password form my licence page but it returns an invalid message.
help ?

using daz 4.9 & octane plug-in 3.05.3

Log in with your Otoy username/password - not the plugin license username/password.

Paul

thanks !

I am failing to authorise OcDS (3.07) too - I am just downloading the 3.08 beta version, plus the 3.08 standalone version of Octane . I mention that last to confirm I am using the Otoy username/password and do not have an access/conenction issue Tried with both user name and user email and stlll get same 'Sign-in error' error message indicating it could not connect to the server

I am failing to authorise OcDS (3.07) too - I am just downloading the 3.08 beta version, plus the 3.08 standalone version of Octane . I mention that last to confirm I am using the Otoy username/password and do not have an access/conenction issue Tried with both user name and user email and stlll get same 'Sign-in error' error message indicating it could not connect to the server

I suggest contacted OTOY directly about this, using the Support->Submit a Request button at the top of this page.

Paul

face_off wrote:

I am failing to authorise OcDS (3.07) too - I am just downloading the 3.08 beta version, plus the 3.08 standalone version of Octane . I mention that last to confirm I am using the Otoy username/password and do not have an access/conenction issue Tried with both user name and user email and stlll get same 'Sign-in error' error message indicating it could not connect to the server

I suggest contacted OTOY directly about this, using the Support->Submit a Request button at the top of this page.

Paul

Hi Paul,

I had done some poking about and it's NOT the plug-in, it's the actual standalone licensing that is failing, not your plug-in. I am composing a support request now.

A bit more investiagtion shows that the fault is at my end, a new wi-fi router seems to be blocking contact to that (account.otoy.com) network:
ping -4 account.otoy.com

Pinging production-sso-webapp-205421376.us-east-1.elb.amazonaws.com [54.165.202.52] with 32 bytes of data:
Reply from 192.168.225.1: Destination net unreachable.
Reply from 192.168.225.1: Destination net unreachable.
Reply from 192.168.225.1: Destination net unreachable.
Reply from 192.168.225.1: Destination net unreachable.

Swapping to another connection (different wi-fi adapter and different ISP):
ping -4 account.otoy.com

Pinging production-sso-webapp-205421376.us-east-1.elb.amazonaws.com [52.0.136.249] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Which whilst still looking like an error, isn't really, as pings are often blocked and will time out, but at least the destination is NOT unreachable