

Note all commands here are case sensitive. It’s worth restarting the http service and confirming both start OK. If the above does not work, you may have a different problem, not currently covered in this guide. A server-based firewall is at most a complement and a secondondary defense for external traffic. The proper place to filter external connections is on the router. Restart the HTTP server / amend configuration # vladv wrote: Unfortunately my current router is a TP-Link which doesn't have inbound filtering and QNAP which can't filter port access. Periodically attempt to reconnect to WinSCP / the Web page, or use QFinder to determine when the QNAP is back online. Leave it to do what it needs to do for at least half an hour. Note it may take a long time for the NAS to reboot.
Qfinder qnap port firewall pro#
Qfinder qnap port firewall update#
A firmware update may cause a mismatch between the config file and the service being run. Sometimes a configuration problem will cause the service to behave badly. The cause can be a number of things, but it boils down to an issue with the http service or proxy service on the QNAP. You’re trying to connect to your NAS’s web interface but it’s just spinning forever and not actually loading.
