using Restart server important bug
-
fasttrackhost
- Posts: 15
- Joined: Tue Feb 05, 2019 7:10 pm
- Os: Ubuntu 17x
- Web: apache
using Restart server important bug
Hi,
using the Restart Server option in vestacp Web Interface will lead you to a page "Not found" server restarts, thats OK, BUT the url is:
"https://host.example.com:8083/restart/s ... xample.com"
So if you try to reload the page it will Restart server again and again and again, every time you try to reload the page thinking it should load the Web Interface again after server restarted.
So it should be changed to go to another URL so when people click Retry or Reload it wont Restart Server again and again.
Even better would be if before sending the Restart instruction to server, send the user to a page where it gives him a message saying something like: "Your server was restarted, you must wait until it fully restarts."
Even more interesting would be a javascript to do a ping each 2 or 3 seconds to see if it is back, and when ping ok, lead the user to the interface. It could be a ping or any query with a small timeout so if it fails, it simply repeats the query.
using the Restart Server option in vestacp Web Interface will lead you to a page "Not found" server restarts, thats OK, BUT the url is:
"https://host.example.com:8083/restart/s ... xample.com"
So if you try to reload the page it will Restart server again and again and again, every time you try to reload the page thinking it should load the Web Interface again after server restarted.
So it should be changed to go to another URL so when people click Retry or Reload it wont Restart Server again and again.
Even better would be if before sending the Restart instruction to server, send the user to a page where it gives him a message saying something like: "Your server was restarted, you must wait until it fully restarts."
Even more interesting would be a javascript to do a ping each 2 or 3 seconds to see if it is back, and when ping ok, lead the user to the interface. It could be a ping or any query with a small timeout so if it fails, it simply repeats the query.