<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nrf9160 AWS FOTA fails after OTA job starts</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/57401/nrf9160-aws-fota-fails-after-ota-job-starts</link><description>My nrf9160 connects to AWS when using the AWS FOTA example. However, when I start the custom job as setup from the following link: 
 
 https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/nrf9160/aws_fota/README.html#configuring 
 </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 06 Feb 2020 12:47:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/57401/nrf9160-aws-fota-fails-after-ota-job-starts" /><item><title>RE: nrf9160 AWS FOTA fails after OTA job starts</title><link>https://devzone.nordicsemi.com/thread/233052?ContentTypeID=1</link><pubDate>Thu, 06 Feb 2020 12:47:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e9e0816-9802-4080-9511-e3cfdf45cc88</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Great to hear! &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf9160 AWS FOTA fails after OTA job starts</title><link>https://devzone.nordicsemi.com/thread/233043?ContentTypeID=1</link><pubDate>Thu, 06 Feb 2020 12:26:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8bc6edce-68c7-4a95-8c6e-438503dc875c</guid><dc:creator>hmichel</dc:creator><description>&lt;p&gt;That worked. Thank you for all the help. I have learned that it is good to delete the old jobs. Thanks for the reminder.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Hilary&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf9160 AWS FOTA fails after OTA job starts</title><link>https://devzone.nordicsemi.com/thread/232894?ContentTypeID=1</link><pubDate>Wed, 05 Feb 2020 15:56:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a9f8e81e-5e43-4c24-b18f-56fac5ed0b15</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello&amp;nbsp;&lt;span&gt;Hiilary,&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I was able to reproduce the error, but could not see what&amp;nbsp;caused it until I looked over your log&lt;/span&gt;&lt;span&gt;&amp;nbsp;one more time, and compared it to mine. I think your job file is the issue.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;In the host part of the job file, you&amp;nbsp;are missing a part of your Object URL of update.bin:&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;Start downloading firmware from s3.us-east-2.amazonaws.com/app_update.bin&lt;/pre&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;While mine is:&lt;br /&gt;&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;Start downloading firmware from nordicoeyvind.s3.eu-north-1.amazonaws.comapp_update.bin&lt;/pre&gt;&lt;br /&gt;After configuring the S3 Bucket permissions and Bucket policy, your Object URL should look like this:&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;&lt;strong&gt;https://&amp;lt;bucket-name&amp;gt;.s3.&amp;lt;region&amp;gt;.amazonaws.com/app_update.bin&lt;br /&gt;&lt;br /&gt;&lt;/strong&gt;&lt;/div&gt;
&lt;div&gt;It may be somewhat clumsy explained in the documentation, but the job file should look like this:&lt;br /&gt;&lt;pre class="ui-code" data-mode="json"&gt;{
  &amp;quot;operation&amp;quot;: &amp;quot;app_fw_update&amp;quot;,
  &amp;quot;fwversion&amp;quot;: &amp;quot;v1.0.2&amp;quot;,
  &amp;quot;size&amp;quot;: 181124,
  &amp;quot;location&amp;quot;: {
    &amp;quot;protocol&amp;quot;: &amp;quot;http:&amp;quot;,
    &amp;quot;host&amp;quot;: &amp;quot;&amp;lt;bucket-name&amp;gt;.s3.&amp;lt;region&amp;gt;.amazonaws.com&amp;quot;,
    &amp;quot;path&amp;quot;: &amp;quot;app_update.bin&amp;quot;
   }
}&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;Please try this and let me know how it goes.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Remember to delete the old job under Manage --&amp;gt; Jobs in IoT Console.&lt;br /&gt;&lt;br /&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf9160 AWS FOTA fails after OTA job starts</title><link>https://devzone.nordicsemi.com/thread/232800?ContentTypeID=1</link><pubDate>Wed, 05 Feb 2020 11:32:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef1079f9-3bd9-44a3-85e2-cc22207859d6</guid><dc:creator>hmichel</dc:creator><description>&lt;p&gt;1) I am running v1.1.0 of NCS.&lt;/p&gt;
&lt;p&gt;2) Per the link for setting up Aws S3 Bucket and as a result addressing the &amp;quot;Content-Range field is missing in the HTTP GET header&amp;quot;&lt;/p&gt;
&lt;p&gt;Here are the bucket policy settings&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1580902064504v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;And here is the content of the json file&lt;/p&gt;
&lt;p&gt;&lt;span style="background-color:#ffffff;"&gt;{&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;,&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;quot;Statement&amp;quot;: [&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; {&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "Effect": "Allow",&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "Principal": "*",&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "Action": "s3:GetObject",&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "Resource": "arn:aws:s3:::mynrf9160fwupdatev2/*"&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; }&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ]&lt;br /&gt;}&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;3) I am able to put the url for the binary in a browser and it will pop up a message in the browser for downloading the file.&lt;/p&gt;
&lt;p&gt;I must be missing something simple&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Hiilary&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf9160 AWS FOTA fails after OTA job starts</title><link>https://devzone.nordicsemi.com/thread/232753?ContentTypeID=1</link><pubDate>Wed, 05 Feb 2020 08:54:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3353bb55-d13c-4b0a-842a-a8aedcb6ec6b</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;First of all, what version of NCS are you running?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""]Server did not send &amp;quot;Content-Range&amp;quot; in response[1B][0m[/quote]
&lt;p&gt;&lt;span&gt;In the AWS_FOTA documentation, it states under troubleshooting:&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Content range is not defined:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;If you host the firmware image on a different server than in an S3 bucket, this error indicates that the Content-Range field is missing in the HTTP GET header. To fix this problem, configure the host server to provide this field. If you are using an S3 bucket, make sure that you have configured it as described in&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/nrf9160/aws_fota/README.html#setting-up-an-aws-s3-bucket"&gt;Setting up an AWS S3 bucket&lt;/a&gt;. Also, confirm that your file is available from the browser without being logged into your AWS account.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Can you please check and verify that this is the issue? If not I will try to reproduce here.&lt;br /&gt;&lt;br /&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>