web interface doesn't work for my NSA325-v2
peppe_sr
Posts: 4 Freshman Member
like object i'm not able to reach my NSA325-v2, trought web interface, if i call the addresse i have this http://puu.sh/FpAzl/4c90794e4b.png
nas is up and available i can connect using the Nas Starter Utility http://puu.sh/FpAAT/b5587a7512.png i can browse all i can write and delete files but i can't configure nothing
could someone point me on a way to solve? is there a way to reset without losing contents? if needed i can try to explain how i broke connection, becaus i'm guilty. thanks!
#NAS_Mar_2020
#NAS_Mar_2020
0
Accepted Solution
-
Hm. Your error, connection refused, tells that the webserver is not listening on port 80 (or 443, depending if you used http or https). That means that the webserver is either not started, or crashed. On firmware 4 the packages run on the same webserver as the webinterface (On fw 5 that is changed. The packages run on a different webserver), so a misbehaving package can crash the server.I think a factory reset is the easiest way to solve this. Press the reset button until the 3th beep. This will delete the configuration, but leave the files on the disks. You'll have to re-create the users, and re-enable the shares.Packages will be disabled. You can enable them again, but that will start them with their original config. You can also delete a packages, and reinstall them, to start with a fresh config.1
All Replies
-
if needed i can try to explain how i broke connection, becaus i'm guilty.
That would certainly help.
Do you have shell access in some way?
0 -
so i was trying to open a folder of the nas to be reached from outside, don't remember how, it occurred a while ago, i was thinking to solve now because i'm working from home and i'm here the whole day. i usede some sort of setting inside the nas configuration and after i confirmed changes web access stopped to work.i never used a shell access, but my administrator account of the nas is valid. could you point me in some direction?0
-
Hm. Your error, connection refused, tells that the webserver is not listening on port 80 (or 443, depending if you used http or https). That means that the webserver is either not started, or crashed. On firmware 4 the packages run on the same webserver as the webinterface (On fw 5 that is changed. The packages run on a different webserver), so a misbehaving package can crash the server.I think a factory reset is the easiest way to solve this. Press the reset button until the 3th beep. This will delete the configuration, but leave the files on the disks. You'll have to re-create the users, and re-enable the shares.Packages will be disabled. You can enable them again, but that will start them with their original config. You can also delete a packages, and reinstall them, to start with a fresh config.1
-
Ok, thanks a lot. I will reset and report.
Peppe0 -
sorry for the long delay, yesterday i resetted my nas and now everything works fine. thanks a lot0
Categories
- All Categories
- 414 Beta Program
- 2.2K Nebula
- 130 Nebula Ideas
- 91 Nebula Status and Incidents
- 5.4K Security
- 173 USG FLEX H Series
- 256 Security Ideas
- 1.4K Switch
- 71 Switch Ideas
- 1K Wireless
- 36 Wireless Ideas
- 6.2K Consumer Product
- 235 Service & License
- 372 News and Release
- 79 Security Advisories
- 24 Education Center
- 5 [Campaign] Zyxel Network Detective
- 2.9K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 80 About Community
- 69 Security Highlight