NRF Cloud - NO green + sign

[SSimon]

Hi!

It must be something stupid from my side.

I'd like to add new device ( first one ) on Dashboard. According the manual I should press on green add sign, but there is no " + sign".

Any suggestion?

Best regards,

Simon.

[Øyvind]

Hello Simon, 

I've never seen that kind of issue before. Have you tried to refresh the page? This is what it should look like:

Kind regards,
Øyvind

[SSimon]

Thank You Øyvind for replay,

Yes I did! I was re_enter ( longing out and in ) several times in past two days.

Simon.

[Øyvind]

What browser are you using? Have you tried another? Did you try with shift+F5? Or CTRL+R?

[SSimon]

Firefox, MS Edge, is the same. No change.

It must be something with Logging In.

[Øyvind]

I will need to forward the login information i.e. email, to our nRF Cloud team. 

Can you please try deleting cookies affiliated with nRF Cloud from your browser history? 

[Øyvind]

We were able to reproduce the issue here. It seems that there is an issue in FireFox. Could you please try with Chrome browser?

[SSimon]

I did clear the cookies. This did not change anything.

I'm shore something went wrong with registration, because I can not delete my account.

I can login from another computer, with the same result -> No + sign.

Another browser will not change anything according My opinion.

Best regards,

Simon

[Øyvind]

In Firefox can you please open the developer tools and open console while logging in to nRF Cloud. This should output errors from the web page. 

Testing Chrome will verify that we are seeing the correct issue and are able to fix.

[SSimon]

After loging:

Firefox can’t establish a connection to the server at wss://a2n7tk1kp18wix-ats.iot.us-east-1.amazonaws.com/mqtt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAZ44I7JQUG7IDJIZM%2F20210902%2Fus-east-1%2Fiotdevicegateway%2Faws4_request&X-Amz-Date=20210902T140011Z&X-Amz-SignedHeaders=host&X-Amz-Signature=b9cb4625421f855a6fabcc7e2de14ff6aecbc52df57fb3517d16d41e84509c26&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEM7%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLWVhc3QtMSJIMEYCIQDlIPklY74bx8IEvHx6g1VfeOvsZ6M4iLoPLV8MWjPu5gIhALbDA267TZgUWhVDha8ZgNgC1MGuKwJbtQHbMGR4R6JMKsQECBcQAxoMNjgwNTAyNzA5Mjg4Igx%2FV3spMVNLPNKF8PAqoQRIasGPk%2F22aH1%2B%2BY3G9Q%2Fi24vdbyRL3X3F5UGeRpsz%2FNjyzyCqzzHnoIYuS8b3RmVteqRvK9L5MxWBAL1ih2FsFc47H8R8RG%2B47%2BfprvZDtvOHXIxnCZnqr3eB216eZvR%2F1Et0H%2BMrm54%2BOqF4BHpBFupWbrM9uICwCBuGllDBcnsU9fUx1YMk2osOHrQ%2F0G6q7NvHBRMRGDgAohPZaj37KA97qqUG0iCR5KhYOrn%2F3WG%2BytCu2jfBle6LJLVQ9kyKFPRU4mRmxdqLN9a0VHyGy7Ejc27NsGVy8Oh8t83uLmeBOUPJL41IqZ3hNGDYs2%2FU2vyHYVqF7H7kgDdPjk9usEoE2p0eIHY6tIfbSBQ0cAAGg65UU63om795gRdKCmnIGs%2FdSofW1u8b5rMEqVY%2FgoADSHGw9%2F5aQdrSMGdgVw8w%2F0FHSYsXZ7gH9qLogNs%2BN8DfWHJR0mcIaIOYzpQTZfapzAXD7AGBoavoso%2FAa%2BqvEPIiJN44%2BgTkl2cZoIzVSeZVoPiOaUXxLQ6FkGaFp9tXfi9NuqL8fCySmtb%2BspXbCICFVtr3cpaZ8IHXIlOfw2cC5jCq92VAwxEgMlvcpS1bdtBcDjSr5hDDJ5MfLiNNN0ERCjzlUeoL2Pgo2Q1jvj%2FLJB7woaDEcvAoPCEYB%2B%2FPqQnlNKgr991Y6CBUoB3unGK%2FeTWggX4eNZECz2dYQzEZ5Y9NcpjOaJ9rpR8a3zCer8OJBjqEAhe1GP62I%2FwLhMVU4O1lMmSIEAtfiYeIr0JY8w%2Bg%2FZ8NdvY92j2TeOTXUz%2FdieiKFPwSy4Wwh0ElH0PyG4hhJFpG%2FiFfgMCFDwKsX2bxAuq7nwTVdd8UKzA9ZDwhDFN%2Bun6cuVOaR1NP20QEF8%2FUcdUbhZ0QtPlYebAbMGb3fjtUiMMXpJ6EAk4gUTuttg%2B2547dzhfWLIwm6YViaXvQvvO79D0j74jeVqbpQKxwoJDlTNp9s%2Fy6dD5UUJcKczegezAcTIO6gQq4mqLs0L6tTqvAu8bMrtVArAbEpVBMJhV0Dn3TJQshe1SV31VyLU45vBd2TQVhmeW15mISWmICBZhGWrL8. app.min.dd7782b8.js:131:12738

Uncaught Error: Unhandled error. (undefined)

[Øyvind]

Thank you for providing this information. I will forward to our nRF Cloud team.

[SSimon]

Dear  Øyvind,

Thank You for help, the team made good job!

Best regards,

Simon.

[Øyvind]

Hi Simon, is your issue fixed?
 

SSimon said:

Uncaught (in promise) InvalidSignatureException: Signature not yet current: 20210902T134316Z is still later than 20210902T134244Z (20210902T133744Z + 5 min.)

Our dev team informs me that AWS endpoints calculate a signature for authenticating request (they do not transmit the actual user secrets), and they are time based, to make these signed requests very short lived.

From the timestamps printed it looks like the users time is a little more than 5 minutes in the future.

The AWS Sig v4 algorithm however only allows for a maximum of 5 minutes: https://docs.aws.amazon.com/general/latest/gr/signing_aws_api_requests.html

Kind regards,
Øyvind