-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document white-listing IPs when using RobotStudio #81
Comments
Copy of the post on the RS forum:
|
Is there something analogous to do when connecting to a real irc5 controller instead of RobotStudio? Currently, I can get the ros driver to work with RobotStudio but not the controller, error being
|
@joedavid-tuni - did you get this to work? I can't get it to work with RobotStudio, even following the instructions above. I still get a "RAPI Unidentified Error" when connecting. Were you able to get it working on a irc5 controller? |
Using a proxy to work-around the HTTP
500
Internal Server Error problems (#47) is OK, but it might be better to use white-listing of IPs which are allowed to access the RWS server instead.While both options will allow access to the machine which is running the Virtual Controller in RS, the proxy approach essentially allows any remote host access, while the white-list will allow only the IPs / hosts which are listed access.
This is more fine-grained and easier to setup as well.
The general procedure is described in Using RobotWebServices to access a remote Virtual Controller on the RS forum.
It would be good to duplicate the steps for this procedure here locally in this repository to avoid depending on external resources (which may go off-line at any moment).
The text was updated successfully, but these errors were encountered: