Since the bionic update I can't start RStudio Server. I'm running R 3.5 and the latest RStudio Server version, but when trying to connect to the http://:8787 it says it can't find the server.
If I launch the terminal and type $ sudo rstudio-server verify-installation, nothing happens, and $ sudo rstudio-server start $ sudo rstudio-server restart
I get: rsession: no process found
I've tried to reinstall it but without success. Any ideas?
Hi, rsession: no process found is just saying that there are no R session currently running, so it doesn't necessarily mean that your RStudio server is not running. Can you try: sudo rstudio-server status?
@edgararuiz thank you for your reply.
The status shows something contradictory to sudo rstudio-server restart.
So to answer your question, it gives the following:
Which clearly isn't true as the restart or stop command shows no process found. So I assume that this is some sort of a bug or so with the new Ubuntu version.
Also not possible as it's a standalone computer and I can't even access when checking it locally. Also nothing changed and the firewall is off. Nevertheless I've added the rule just in case to have that port open and checked if it was listening on that port which it is.
Everything was fine before the update to Ubuntu 18.04. After the update this started to happen.
It works with localhost. However, if I type the ip address of the machine but locally it doesn't work. Only using the localhost path which is strange because it always worked before with the ip.
The strange part here is that the firewall is disabled, and on the local machine it suddenly started working when using the localhost path. However, if I try to access it from a remote machine it doesn't work. But supposedly it is listening, so I'm not sure what could be the problem here.
I've contacted the network guys and they changed nothing in the network.
After I've reinstalled everything and suddenly everything works. I had tried to reinstall rstudio server before without removing the /etc/rstudio folder, which could have been the conflicting one.
Now I can access everything and connect from a remote machine. However, I'm still not sure what caused this.