0
all right?
See if you can help me with a question. I use Rshiny for a Dashboard where I work, last month we migrated this application to a virtual machine (aws), installed the Rstudio server and accessed it via browser, so far all without problem.
The problem is when I run Rshiny, there are no errors, and Shiny does not go up.
I’ll give you the details about this: on ec2 I have the public IP address and the private one, to move up the application I am using the Private IP at port 3000. I’ve already released this ip in my firewall.
Here fits an important detail, in ec2 we have the public and private ip, when I run my application in public, generates error:
Listening on http://xx.xx.xx.xx:3000
createTcpServer: address not available
Error in initialize(...) : Failed to create server
In Rshiny, I use the function:
options(shiny.port = 3000)
options(shiny.host = "xx.xx.xx.xx") #Utilizando IP privado para subir.
Look, I’ve cleared the doors on the EC2.
These are two options that I’m basically trying to find the solution, one using the public ip (generates the above error), and also upload Shiny with the private ip that does not generate any error, but generates message that "it took a long time to answer".
I don’t know what that problem could be.