albert wrote:Sorry, no that's not the problem, as said command line does work fine.
Sure?
The message "No functional Internet connection was found" has to come from apt; the web interface just echo's this response. Assuming earlier reported cases are correct in that this is the result of a DNS lookup time-out, the straightforward conclusion would therefore have to be that the web application either shuts something down that it shouldn't (but then other people would experience the same problem, right?) or somehow puts too much strain on the system (which you should be able to avoid by shutting down other high memory and/or CPU utilizing services).