Hi @tomasj7 ! Thanks so much for asking this question! Apologies for the delayed response!
This may be a question that is worth passing along to our support team (support@rstudio.com). If you do, please share the link to this community post so they have this background!
Are you trying to publish from RStudio Server to RStudio Connect? It sounds to me like wherever your R session is running does not have network access to the RStudio Connect host. Do you mind saying a little something about where your R code is running, what your architecture / networking looks like, etc.?
> httr::http_status(httr::GET("https://RSTUDIO_CONNECT_SERVER"))
Error in curl::curl_fetch_memory(url, handle = handle) :
Timeout was reached: [RSTUDIO_CONNECT_SERVER] Connection timed out after 10001 milliseconds
rsconnect::addConnectServer was possible to do, but connectUser also return problem
> rsconnect::connectUser(account = 'myaccount', server = 'RSTUDIO_CONNECT_SERVER')
Error in curl::curl_fetch_memory(url, handle = handle) :
Timeout was reached: [RSTUDIO_CONNECT_SERVER] Connection timed out after 10001 milliseconds
Timing stopped at: 0 0.012 10.01
And machines can ping each other.
But from local desktop version (RStudio IDE) everything working fine.
This "timeout" issue here is canonically a network issue. In cloud environments like AWS, it typically means that the Security Group associated with the Connect instance is not letting traffic through on the port you are requesting (from the place you are requesting from - in this case RSP).
I would try taking a look at your networking security setup, what firewalls and such are present, and ensure that RStudio Server Pro can actually make requests to RStudio Connect.
Sorry for the delay here @michalslovik! I'm not sure why it didn't let me know that you had responded. Are you still experiencing trouble? If so, please open a support request by emailing support@rstudio.com !
Ultimately the ports you mention (if that is where the products are listening) should be open. You can test connectivity from the terminal on each server with netcat using something like:
If this times out, it means that a connection to that host / port from the server you are currently on is not working for some reason or another. Security Groups are definitely the most common culprit.