You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RStudio Version 2023.08.0-daily+46
R-4.1.0
rsconnect
RemoteType: github
RemoteSha: a3d883c
Problem: The rsconnect::restartApp() function is designed to work exclusively with Shiny Servers. However, when a user attempts to use it for an app deployed on a Connect server, the logs provide inaccurate feedback.
Steps:
Deploy an app on Posti Connect
Navigate to IDE --> console
Run rsconnect::restartApp( appName = "Your_app_name", server = "test_box", account = "Your_account_name")
Actual Result:
restarting fails with the following error message
rsconnect::restartApp(appName = "appname", account = "testaccount",
server = "test_box")
Restarting application...
Error in `POST()`:
! <http://xxxxxxx:xxx/__api__/applications/xxxx/deploy> failed with
HTTP status 500
Run `rlang::last_trace()` to see where the error occurred.
> rlang::last_trace()
<error/rsconnect_http_500>
Error in `POST()`:
! <http://xxxxxxxx:xxxx/__api__/applications/xxxx/deploy> failed
with HTTP status 500
The text was updated successfully, but these errors were encountered:
* enforce that the target server is shinyapps.io
addAuthorizedUser
removeAuthorizedUser
showUsers
showInvited
resendInvitation
configureApp
setProperty
unsetProperty
purgeApp
restartApp
terminateApp
showUsage
showMetrics
Fixes#863Fixes#864
* always with the trailing whitespace
* documentation
> rsconnect::restartApp( appName = "purgeapp-retest", server = "test_box", account = "chaitatest")
Error in `rsconnect::restartApp()`:
! `server` must be shinyapps.io
Run `rlang::last_trace()` to see where the error occurred.
RStudio Version 2023.08.0-daily+46
R-4.1.0
rsconnect
RemoteType: github
RemoteSha: a3d883c
Problem: The rsconnect::restartApp() function is designed to work exclusively with Shiny Servers. However, when a user attempts to use it for an app deployed on a Connect server, the logs provide inaccurate feedback.
Steps:
Actual Result:
restarting fails with the following error message
The text was updated successfully, but these errors were encountered: