Blue LED Blinking and no network access to 2Big Network

[Jocko]

So nothing wrong on these outputs and the web-server seems to run rightly.

We go to restore the default credentials for firmware web-interface. Then run the command

Code: Select all

restore_adminpassword

and try to log in the console with the credentials admin-nas/admin

[PaaNooS]

So nothing wrong on these outputs and the web-server seems to run rightly.

We go to restore the default credentials for firmware web-interface. Then run the command

Code: Select all

restore_adminpassword

and try to log in the console with the credentials admin-nas/admin

OK. I can login

[fvdw]

Mention that new login password is 4-letters, if it matters

Be aware username and password are case sensitive in linux environment

[PaaNooS]

So 2 last questions

1. Can I change my credentials?
2. How can I build RAID 1. Now I've installed only one hard disk

[Jocko]

:thumbup

Now, you have to install the patch for version 18-2.

After doing it try again to change the admin credentials as you did previously and run again an upgrade (yes you can do it even if it claims you already have the latest version)
Then check if you can still login and in this case you have to install again the patch for version 18.2

[Jocko]

For point 2, I'd rather we fix definitively your credentials issue

[PaaNooS]

OK I have to leave now

Many many thanks for now

Have a nice weekend. See you at Monday

[PaaNooS]

Hello guys

I have some good news.

After installing 18.2 patch I changed my credentials and CAN login without problem
I tried to login even after restart and shutdown/power up my NAS without any problem
After this I put second hard disk to right-hand bay and followed the steps to build RAID 1 with success.
The only thing I mentioned is that after RAID 1 building public folder was disappeared and had to make a new

So at this time everything seems to work perfect

PS. Another issue I mentioned is that I can login to my NAS even after NAS restart or restart my browser without entering my credentials.
That happens after 18.2 patch installation

[PaaNooS]

I'd like to enable mail notifications but I'm a little confused

To 'Credentials parameter' I have to write my NAS login credentials, or my mail server credentials ??

I've tried both of them but cannot receive any test mail

[Jocko]

Hi

According with some google searches ("otenet email settings smtp"), you have to use the port 465 instead of 587. Credentials is your email address and your Otenet.gr password. I think you have to enable TLS ("Enforce TLS" option).
Note: I removed your menu capture, as everyone may get your email address)

After installing 18.2 patch I changed my credentials and CAN login without problem
I tried to login even after restart and shutdown/power up my NAS without any problem
After this I put second hard disk to right-hand bay and followed the steps to build RAID 1 with success.
The only thing I mentioned is that after RAID 1 building public folder was disappeared and had to make a new

So at this time everything seems to work perfect

Nice !
Just to my perfect information what guidance did you use? Do it directly from the firmware interface ? In this case, you had to notice the warning about all data will be lost by setting the raid

PS. Another issue I mentioned is that I can login to my NAS even after NAS restart or restart my browser without entering my credentials.
That happens after 18.2 patch installation

Thank you for the feedback. It is not related with the patch but at least with Firefox.

I made some tests :
- with Edge or Chrome, you get the expected behaviour (login window after reopening the browser or you made a close action from the web-interface)
- Firefox, you get the expected behaviour after closing all FF windows (browser, download window,...). You get a login window if you reopen FF. Please to note there is a small delay so that all FF threads are unloaded when you close the browser window. If you reopen FF before, no login window may be required if the related thread is not yet unloaded.
But there is an issue with the close action where no login is required if you reload the firmware. So I need to investigate this last point :whistle