Error 203 when upgrading to version17

[Gilbert115]

I'm getting the following when trying to update the firmware to 17.0 using Firmware Update in the web interface:

Firmware upgrade step 1 started:
Search firmware version information for cloudbox ....
The latest version available from http://plugout.net is: fvdw-sl 17.0

Get the bound upgrade files list
Failed to download the upgrade files list
Error 203

What am I doing wrong?

[Jocko]

Hi Gilbert115,

To get the error code 203 that means our server (plugout.net) returns a HTML error code (404, 403, 500,...) when your nas tries to download a file.
From plugout log the error code is 403, so forbidden request. That means the previous step (NAS login) failed and the NAS tries to download a file with the anonymous account what is forbidden.

This is confirmed when I looked at the sessions opened by the NAS (many attempts found). All your download requests were done with the account "anonymous".

As it is working with the other members I think the issue is how the NAS has an Internet access.

After logging, the firmware parses the logging request header to detect the session id and re-uses it when it tries to download a file. That would mean it fails at this step. This may happen if the header content is not as expected. For example if you use a proxy or a google proxy to compress data (in this last case you have an inconsistency IP issue)

To valid this do

Code: Select all

cd /tmp
wget -U "test" -d "http://plugout.net"

and post the output

[Gilbert115]

Where do I enter the code? I'm using a Mac but have access to a PC if needed.

[Jocko]

Hi

You can use your MAC (with windows OS you would need to install an additional app : eg Putty).

So open your Terminal application and type this command

Code: Select all

ssh root@nasip

and enter its related password. (If you don't change the default password, it is "giveit2me")
Note: "nasip" is the IP of your NAS (ex: 192.168.xx.yy)
Note2: if it is the first access you try, you have to confirm the authenticity of the NAS (=> answer 'yes')

Then after opening the shell session on your NAS, you should be able to enter the command-lines I gave previously.

[Gilbert115]

Thank you. Here's the output:

Code: Select all

DEBUG output created by Wget 1.15 on linux-gnueabi.

--2017-11-20 17:31:18--  http://plugout.net/
Resolving plugout.net... 213.186.33.24, 2001:41d0:1:1b00:213:186:33:24
Caching plugout.net => 213.186.33.24 2001:41d0:1:1b00:213:186:33:24
Connecting to plugout.net|213.186.33.24|:80... connected.
Created socket 3.
Releasing 0x0007d298 (new refcount 1).

---request begin---
GET / HTTP/1.1
User-Agent: test
Accept: */*
Host: plugout.net
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 200 OK
Set-Cookie: clusterBAK=R1564869292; path=/; expires=Mon, 20-Nov-2017 23:48:40 GMT
Date: Mon, 20 Nov 2017 22:31:18 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Set-Cookie: cluster=R2881519971; path=/; expires=Mon, 20-Nov-2017 23:43:22 GMT
Server: Apache
X-Powered-By: PHP/7.0.23
Set-Cookie: phpbb3_hy4o6_u=1; expires=Tue, 20-Nov-2018 22:31:18 GMT; path=/; domain=plugout.net; HttpOnly
Set-Cookie: phpbb3_hy4o6_k=; expires=Tue, 20-Nov-2018 22:31:18 GMT; path=/; domain=plugout.net; HttpOnly
Set-Cookie: phpbb3_hy4o6_sid=ebf0939f558ed862b46945ba947bd0ad; expires=Tue, 20-Nov-2018 22:31:18 GMT; path=/; domain=plugout.net; HttpOnly
Cache-Control: private, no-cache="set-cookie"
Expires: 0
Pragma: no-cache
Vary: Accept-Encoding
X-IPLB-Instance: 802

---response end---
200 OK

Stored cookie plugout.net -1 (ANY) / <permanent> <insecure> [expiry 2017-11-20 18:48:40] clusterBAK R1564869292

Stored cookie plugout.net -1 (ANY) / <permanent> <insecure> [expiry 2017-11-20 18:43:22] cluster R2881519971
cdm: 1 2
Stored cookie plugout.net -1 (ANY) / <permanent> <insecure> [expiry 2018-11-20 17:31:18] phpbb3_hy4o6_u 1
cdm: 1 2
Stored cookie plugout.net -1 (ANY) / <permanent> <insecure> [expiry 2018-11-20 17:31:18] phpbb3_hy4o6_k
cdm: 1 2
Stored cookie plugout.net -1 (ANY) / <permanent> <insecure> [expiry 2018-11-20 17:31:18] phpbb3_hy4o6_sid ebf0939f558ed862b46945ba947bd0ad
Registered socket 3 for persistent reuse.
Length: unspecified [text/html]
Saving to: ‘index.html’

    [ <=>                                   ] 24,418      --.-K/s   in 0.09s   

2017-11-20 17:31:18 (255 KB/s) - ‘index.html’ saved [24418]

[Jocko]

So currently there is no issue.

Check now if you can open a session on plugout with your account :

Code: Select all

/usr/bin/curl -i -c /tmp/cookie.txt -b /tmp/cookie.txt -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:49.0)"  -X POST -d username="Gilbert115" -d password="yourpassword" -d login=login -o '/tmp/login.html' http://plugout.net/ucp.php?mode=login

(change yourpassword by your real password)
Then do

Code: Select all

grep 'X-IPLB-Instance' /tmp/login.html -B 99

and post the output

[Gilbert115]

Did as instructed & here's the output:

Code: Select all

Set-Cookie: clusterBAK=R1564863847; path=/; expires=Tue, 21-Nov-2017 05:12:08 GMT
Date: Tue, 21 Nov 2017 03:55:40 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Set-Cookie: cluster=R1649235384; path=/; expires=Tue, 21-Nov-2017 05:14:54 GMT
Server: Apache
X-Powered-By: PHP/7.0.23
Set-Cookie: phpbb3_hy4o6_u=1; expires=Wed, 21-Nov-2018 03:55:40 GMT; path=/; domain=plugout.net; HttpOnly
Set-Cookie: phpbb3_hy4o6_k=; expires=Wed, 21-Nov-2018 03:55:40 GMT; path=/; domain=plugout.net; HttpOnly
Set-Cookie: phpbb3_hy4o6_sid=4e8adf4b00db8650cb0c16fdc19e89ed; expires=Wed, 21-Nov-2018 03:55:40 GMT; path=/; domain=plugout.net; HttpOnly
Set-Cookie: phpbb3_hy4o6_u=7021; expires=Wed, 21-Nov-2018 03:55:40 GMT; path=/; domain=plugout.net; HttpOnly
Set-Cookie: phpbb3_hy4o6_k=; expires=Wed, 21-Nov-2018 03:55:40 GMT; path=/; domain=plugout.net; HttpOnly
Set-Cookie: phpbb3_hy4o6_sid=a17da2e7fa5d0fcd98f07ffac6d3fc77; expires=Wed, 21-Nov-2018 03:55:40 GMT; path=/; domain=plugout.net; HttpOnly
Cache-Control: private, no-cache="set-cookie"
Expires: 0
Pragma: no-cache
Vary: Accept-Encoding
X-IPLB-Instance: 17308

I see that the username & password is what I use on this site. But I don't use that anywhere in fvdw. Not sure if that means anything, but I thought I'd mention it.

[Jocko]

So there is no issue with the login step.

I see that the username & password is what I use on this site. But I don't use that anywhere in fvdw. Not sure if that means anything, but I thought I'd mention it.

Indeed the firmware uses its own account.

However after some login attempts, a captcha challenge is added when you try to login. firmware install script can not succeed it and then it downloads files with the anonymous account. Maybe it was the case.
So try again to install the last version. I removed all your old sessions opened previously by your attempts. You have now a clean state on our server side. (Please to note 3 members succeeded to upgrade their NAS since Sunday). If it fails (do only one attempt), post the content of these files :

Code: Select all

cat /tmp/upgrade/cook.txt
cat /tmp/upgrade/cookjar.txt

and attach the file /tmp/upgrade/fvdwsl_board_xxxx (you should find a file beginning by 'fvdwsl_board_')

[Gilbert115]

That worked and the upgrade installed without any issues.

Thanks for your help!

[Jocko]

So it is the captcha issue.

This may happen for example if you do several attempts with your account to connect to our site (eg you forgot your password) and at the same time you try to upgrade the firmware. As it is the same IP, a captcha challenge will be also asked on the NAS login request.