DLNA not working with iphone app

Hi,
I have a Flint with 4.1 firmware.
I have a strange problem with the DLNA server, it is not accessible from the iPhone app:

If I click on Network storage nothing happens.
I’m connected locally, as you can see from the screenshot.
I also had another issue with the DLNA server, that it was not able to see files in the USB key (tried two different USB keys) but now is working, if I will be able to replicate the issue I will check in this forum.
cheers
Piero

Can you check the App’s log for it? logs can be enable in the settings icon in the sidebar.

Hi,
I have the log from the “log storage” section, about nas:



2023-03-01 06:37:59.556851
*** Request ***
uri: https://192.168.8.1:6000/GL_NAS_USER_LOGIN
data:
{name: root, pwd: *********************}

2023-03-01 06:37:59.605187
*** Response ***
uri: https://192.168.8.1:6000/GL_NAS_USER_LOGIN
Request Data: {name: root, pwd: *******************}
Response Text:
{“result_code”:5}

2023-03-01 06:37:59.733815
*** Request ***
uri: https://192.168.8.1:6000/GL_NAS_USER_LOGIN
data:
{name: root, pwd: ************************}

2023-03-01 06:37:59.751818
*** DioError ***:
uri: https://192.168.8.1:6000/GL_NAS_USER_LOGIN
DioError [DioErrorType.other]: SocketException: Connection refused (OS Error: Connection refused, errno = 61), address = 192.168.8.1, port = 58886



and also the log you asked from the log-windows:

2023-03-01 06:37:26.857418
*** Response ***
uri: http://192.168.8.1/rpc
Request Data: {“jsonrpc”:“2.0”,“method”:“call”,“params”:[“aBfrWR4EgdRXTtzJaCF2MesWJOUOP4uY”,“repeater”,“get_status”,{}],“id”:1}
Response Text:
{“id”:1,“jsonrpc”:“2.0”,“result”:{“state_name”:“idle”,“eap”:false,“state”:0}}

2023-03-01 06:37:26.868549
*** Response ***
uri: http://192.168.8.1/rpc
Request Data: {“jsonrpc”:“2.0”,“method”:“call”,“params”:[“aBfrWR4EgdRXTtzJaCF2MesWJOUOP4uY”,“tethering”,“get_status”,{}],“id”:1}
Response Text:
{“id”:1,“jsonrpc”:“2.0”,“result”:{“err_msg”:“No device found. Please insert”,“err_code”:-2}}

2023-03-01 06:37:26.874136
*** Response ***
uri: http://192.168.8.1/rpc
Request Data: {“jsonrpc”:“2.0”,“method”:“call”,“params”:[“aBfrWR4EgdRXTtzJaCF2MesWJOUOP4uY”,“cable”,“get_status”,{}],“id”:1}
Response Text:
{“id”:1,“jsonrpc”:“2.0”,“result”:{“status”:1,“mode”:0,“protocol”:“dhcp”,“ipv4”:{“gateway”:““,“dns”:[“89.101.160.4”,“89.101.160.5”],“ip”:”/23”}}}

2023-03-01 06:37:26.881889
*** Response ***
uri: http://192.168.8.1/rpc
Request Data: {“jsonrpc”:“2.0”,“method”:“call”,“params”:[“aBfrWR4EgdRXTtzJaCF2MesWJOUOP4uY”,“modem”,“get_status”,{}],“id”:1}
Response Text:
{“id”:1,“jsonrpc”:“2.0”,“result”:{“modems”:[],“new_sms_count”:0}}

2023-03-01 06:37:29.383180
*** Request ***
uri: https://192.168.8.1:6000/GL_NAS_USER_LOGIN
data:
{name: root, pwd: *********************}

2023-03-01 06:37:29.430924
*** Response ***
uri: https://192.168.8.1:6000/GL_NAS_USER_LOGIN
Request Data: {name: root, pwd: **********************}
Response Text:
{“result_code”:5}

2023-03-01 06:37:29.432943
*** Request ***
uri: http://192.168.8.1/rpc
data:
{“jsonrpc”:“2.0”,“method”:“call”,“params”:[“aBfrWR4EgdRXTtzJaCF2MesWJOUOP4uY”,“nas-web”,“set_nas_ser”,{“enable”:1}],“id”:1}

2023-03-01 06:37:29.436453
*** Request ***
uri: http://192.168.8.1/rpc
data:
{“jsonrpc”:“2.0”,“method”:“call”,“params”:[“aBfrWR4EgdRXTtzJaCF2MesWJOUOP4uY”,“nas-web”,“get_status”,{}],“id”:1}

2023-03-01 06:37:29.463282
*** Response ***
uri: http://192.168.8.1/rpc
Request Data: {“jsonrpc”:“2.0”,“method”:“call”,“params”:[“aBfrWR4EgdRXTtzJaCF2MesWJOUOP4uY”,“nas-web”,“get_status”,{}],“id”:1}
Response Text:
{“id”:1,“jsonrpc”:“2.0”,“result”:{“enable”:1}}

2023-03-01 06:37:29.464996
*** Request ***
uri: http://192.168.8.1/rpc
data:
{“jsonrpc”:“2.0”,“method”:“call”,“params”:[“aBfrWR4EgdRXTtzJaCF2MesWJOUOP4uY”,“nas-web”,“get_proto_config”],“id”:1}

2023-03-01 06:37:29.528587
*** Response ***
uri: http://192.168.8.1/rpc
Request Data: {“jsonrpc”:“2.0”,“method”:“call”,“params”:[“aBfrWR4EgdRXTtzJaCF2MesWJOUOP4uY”,“nas-web”,“get_proto_config”],“id”:1}
Response Text:
{“id”:1,“jsonrpc”:“2.0”,“result”:{“res”:[{“enable”:1,“port”:0,“name”:“samba”,“wan_access”:1},{“port”:6008,“name”:“webdav”,“wan_access”:1,“ssl_enable”:0,“enable”:1},{“enable”:1,“port”:0,“name”:“dlna”,“media_dir”:“/disk1_part1”}]}}

2023-03-01 06:37:29.552022
*** Response ***
uri: http://192.168.8.1/rpc
Request Data: {“jsonrpc”:“2.0”,“method”:“call”,“params”:[“aBfrWR4EgdRXTtzJaCF2MesWJOUOP4uY”,“nas-web”,“set_nas_ser”,{“enable”:1}],“id”:1}
Response Text:
{“id”:1,“jsonrpc”:“2.0”,“result”:[]}

2023-03-01 06:37:29.553454
*** Request ***
uri: https://192.168.8.1:6000/GL_NAS_USER_LOGIN
data:
{name: root, pwd: ************************}



both logs was created when I click on “network storage” on the first page of the application.
I deleted the password (that is correct 100%) I don’t think there are other sensible information, in case let me know or delete the lines that you think are sensible.

thanks
regards
Piero

Just to add one thing, I manually deleted my password from the above logs.
I think that it’s not good write the full password in the log file.
Can I suggest to mask the password from the log? something like *******LAST4DIGIT.
Thanks
regards
Piero

The logs look like a firmware issue, can you try upgrading to 4.2.0 release2?

Hi, thanks for the suggestion. Just one thing, the version 4.2.0 is still in beta.
I have few work around in this moment to manage the file in the USB key, I would prefer to stay in the stable version.
Do you know when you will release the 4.2 version as stable?
Cheer
Piero

It is in the final acceptance test. If it passes the tests, it will become an official firmware release and be migrated to stable version.

Hi Yuxin,
thanks for the answer, I will wait to upgrade when will be official firmware stabe release, that for what I understan will be soon!
After that I will check if I have the same issue.
have a good day.
Cheers
Piero