[Help] F5-221, unable to use the web-ui after updating

[nice555]

Hi there, I need help with my TNAS as it is not working.

I'm using F5-221 and have recently just updated my TNAS to 6.0.770, however it seems that accessing the web-ui does not seem to work. Refreshing the browser after I log in gives a "502 Bad Gateway"

I have tried many ways to deal with the problem, such as taking out the HDD bays. I have access to a monitor and keyboard only to be greeted by a "booting from RAID system" which does not go away no matter if I reinserted the HDD back or not. I do not seem to get anything from the TNAS PC app as well; it says it's offline.
Initialisation seems to work fine with HDD back in according to my monitor, everything works okay.
Transferring files and qBittorrent works as well seperately, but accessing the web-ui using browser is impossible.

Anybody can help what to do after this? If there are ways that could be used with just a keyboard to plug in the NAS it would be handy as well.
Thank you

[EriChan]

Regarding the "502 Bad Gateway" error and web page inaccessibility issues you encountered with your F5-221 after updating to TOS 6.0.770, here is our analysis and recommendations:

• Your file transfers and qBittorrent are functioning normally, indicating that the system kernel and RAID array have been successfully mounted, and the underlying network services are operational.

• The 502 Bad Gateway error typically means that the front-end page cannot obtain a response from the back-end service. This could be due to the related services not starting properly after the upgrade or the root directory being full, preventing the configuration from loading.

Please try the following troubleshooting steps:

1. Log in to the TNAS terminal via SSH using root user privileges , and execute the following instrcution to restart the web service:

Code: Select all

service nginx start

Refresh the TOS page.

2. Check the status of key services:

Code: Select all

systemctl status nginx.service
systemctl status TOSDaemon.service
systemctl status redis.service

Check if these core services are running normally. If any service fails, try restarting it (systemctl restart service name).

3. If the above services fail to restart, it is highly likely that the system root directory is full during the upgrade process.Execute the command:

Code: Select all

df -h

View the line where the mount point is / or contains md9. If Use% shows 100%, try cleaning up large files or logs that were accidentally written.

4. If restarting the Nginx service does not resolve the issue, stop the Nginx service, replace the existing Nginx configuration files with the initial configurations, and then restart the Nginx service:

Code: Select all

service nginx stop
cp /etc.default/nginx/nginx-extend.conf /etc/nginx
cp /etc.default/nginx/nginx-http.conf /etc/nginx
cp /etc.default/nginx/nginx.conf /etc/nginx
service nginx start

After completion, refresh the browser and try logging in.

5. If none of the above methods work, we recommend reinstalling TOS to fix the problem.Additionally, even if the above methods resolve the issue, the cause of the error is still unclear, and other potential issues may exist. For stability and security, we still recommend that you reinstall TOS.