@Michel Kohanim

 

I have a report of the Portal not accepting HTTP GET Rest requests and have verified I can also not make the requests

Error Code: 423

Response: Requested ISY not found in the user's domain

1 hour ago, Javi said:

@Michel Kohanim

 

I have a report of the Portal not accepting HTTP GET Rest requests and have verified I can also not make the requests

Error Code: 423

Response: Requested ISY not found in the user's domain

Use the same credentials you used to login to ISY Portal. Then make sure the ISY is in the account and has been authorized. Round indicator must be green.

Benoit

1 hour ago, bmercier said:

Use the same credentials you used to login to ISY Portal. Then make sure the ISY is in the account and has been authorized. Round indicator must be green.

Benoit

Hi @bmercier,

The credentials are valid and the Socket is working however REST commands are failing with the 423 error. This can be replicated in the (Chrome) browser also.

 

https://my.isy.io/isy/XXXXXX:443/rest/nodes/22 89 3A 1/cmd/DOF

Where XXXXX is URL to ISY

Returns "Requested ISY not found in the user's domain"

Edited March 29, 20205 yr by Javi

Hi @bmercier,
The credentials are valid and the Socket is working however REST commands are failing with the 423 error. This can be replicated in the (Chrome) browser also.
 
https://my.isy.io/isy/XXXXXX:443/rest/nodes/22 89 3A 1/cmd/DOF
Returns "Requested ISY not found in the user's domain"

I know the credentials are valid. Please do what I recommended.


Sent from my iPhone using Tapatalk

1 minute ago, bmercier said:

I know the credentials are valid. Please do what I recommended.


Sent from my iPhone using Tapatalk

@bmercier maybe I am missing something, can you be more specific?  This error appears to have started today.  The indicator is Green,  I am (and have been) using the credentials used for the Portal.  Not sure why the SOAP Socket would work with this URL/credentials and REST would fail.

@bmercier maybe I am missing something, can you be more specific?  This error appears to have started today.  The indicator is Green,  I am (and have been) using the credentials used for the Portal.  Not sure why the SOAP Socket would work with this URL/credentials and REST would fail.

When logging in to ISY Portal, try to use web access to turn off the device in question. If this works (it should), you can see the URL used in the developer console (use F12 to open it).

If it doesn’t work in a browser, then it must be that the URL or the credentials are different.


Sent from my iPhone using Tapatalk

24 minutes ago, bmercier said:

When logging in to ISY Portal, try to use web access to turn off the device in question. If this works (it should), you can see the URL used in the developer console (use F12 to open it).

If it doesn’t work in a browser, then it must be that the URL or the credentials are different.


Sent from my iPhone using Tapatalk

Thanks, it appears that adding the port after the URL is causing the error.  Was this changed?

 

Edit: Sorry, it appears I made this change adding the port about a month ago. Not sure why it only presented itself now.

Edited March 29, 20205 yr by Javi

1 hour ago, Javi said:

Thanks, it appears that adding the port after the URL is causing the error.  Was this changed?

 

Edit: Sorry, it appears I made this change adding the port about a month ago. Not sure why it only presented itself now.

There has been no changes to this area of ISY Portal for a very long time (Years).

Specifying the 443 port should not cause a problem, it's the port used by default when using https, but it's also completely unnecessary. I think the browser might had the authorization header set for different credentials in cache, and removing the 443 might have reset/changed it (?).

Benoit

 

 

Thanks for your time and my apologies for not catching something so simple before posting.

It was an error on my side, my app was adding the port to the wrong location (...isy.io/isy/XXXX:PORT instead of my.isy.io:PORT). I guess I have only used local connection for the past month.

15 hours ago, Javi said:

Thanks for your time and my apologies for not catching something so simple before posting.

It was an error on my side, my app was adding the port to the wrong location (...isy.io/isy/XXXX:PORT instead of my.isy.io:PORT). I guess I have only used local connection for the past month.

No worries