I was testing my first OpenCPU project, having the web test page in the same server than OpenCPU and the R package (an Ubuntu 14.04 server installed in a virtual machine inside Windows Server) it works fine, but I'll probably need the website to be in the Windows Server and OpenCPU (so R too) running in the virtual machine, so I tried the seturl function from OpenCPU to do that, but I got an error which says "that can be fixed enabling CORS in the server"
Looking for a solution I found http://enable-cors.org/server_apache.html In this article is told how to enable CORS in Apache, but what I couldn't find was what folder needs the permission to make OpenCPU remotely works.
This is how I call the package on virtual's machine server
ocpu.seturl("http://virtualmachine_ipaddres/ocpu/library/PruebaR/R")
I tried giving the permissions to the R folder and others but still not working. Any ideas?
Thank you for your help
Related
I'm trying to install the cache server for OpenCPU (I need to enable caching) on an Ubuntu 16.04 EC2 instance. A dependency of opencpu-cache is the latest version of nginx (I can't install the cache server without it).
After I had already installed OpenCPU and verified that it was working, I installed nginx and then opencpu-cache. After installation, however, I can no longer make HTTP or HTTPS requests to the server. Entering both the public IP address and public DNS from the AWS console into my web browser fails to yield a landing page for the server, whereas it was working fine before I installed nginx.
My security rules on AWS are set up correctly (i.e. they're allowing the right ports for HTTP and HTTPS), so what is the issue? All my packages on the server are also up-to-date. SSH sessions work just fine still. I just can't figure out what the issue is.
Nevermind, it turns out that sudo service opencpu-cache restart did the trick lol. Props to Jeroen above.
Good morning,
Working on installing Meteor on windows using the following guide:https://gist.github.com/gabrielhpugliese/5855677
As pointed out on other posts its a little dated and I needed to install meteor separately, which I used this guide: Unable to install meteorite on Ubuntu VM
Currently, my set up can do the following:
files stay in sync between vagrant and windows
localhost:3000/ is working on the server
What I still need help completing:
when opening localhost:3000/ in my windows browser, I get the "This webpage is not available
I know that the vagrant VM is correctly serving the app because I opened a new instance of vagrant and curled the localhoust:3000/
I am actively working in django and node and can successfully run apps locally on :8000 and :8080, I tested the meteor app on those ports but still couldn't connect. I also created a windows firewall port exception on 3000 but the results didn't change.
I know that there is a windows-preview currently out, but that is not working for me and I have an issue being tracked in gitHub.
Thank you in advance.
One thing that might be worth mentioning is it is somewhat possible to use Meteor on windows.
More details here: https://github.com/meteor/meteor/wiki/Preview-of-Meteor-on-Windows.
With your vagrant machine it sounds like there is a problem with port forwarding on your localhost machine to the VM's ports.
One possible simple way to get passed this is to get your Ubuntu machines IP address and simply load it up using http://<ip address>:3000.
I'm not sure why the port forwarding isn't working on your machine. In general the reason is provided when you run vagrant up, if there was an issue.
After updating R from 3.0.2 to 3.0.3 and updating the shiny package the applications I wrote are no longer accessible from remote hosts. They work fine when accessed from machine they are running on using http://localhost:8101. The host OS is Windows Server 2008R2.
I have the feeling that there is a setting a config file that is disallowing access from remote hosts. Where is shiny-server.conf on Windows? I searched for it but could not find it.
Thanks.
you could run app using host parameter:
runApp("you_app", host="0.0.0.0")
and it should be vailable from outside (if there is not any firewall/apache/proxy etc)
Default value for host is 127.0.0.1.
I am transitioning my debian setup into one where all debian-repository external apps run in dedicated docker containers.
In this context rstudio, of which I am a heavy user, has me puzzled ... does anybody have insight into whether it's possible to run it as a client to remote R installation?
What is a very cool feature of RStudio is RStudio Server. You install RStudio Server on you Ubuntu server and log in to a specific port where RStudio Server is running. You then get your full RStudio interface in your web browser. This allows you to run all your R analyses from any computer that has a modern browser and an internet connection.
R then runs on the remote server, asking almost no resource from the computer you are connecting from.
I have installed Web Deploy 3.5 on Windows Server 2008 R2 and tried to run remote publish web application through visual studio 2012. However, I got the error - Destination Not Reachable.
I read some post and checked below and still got no luck.
Firewall was off
Both Web Management Service and Web Deployment Agent Service were restarted and running
Tried to open https://[server]:8172/msDeploy.axd in a browser and it is reachable. (Use default 8172)
Tried to use http://[server]/MsDeployAgentService and it is working with Admin username/password.
Did I miss anything? Thanks.
Maybe same issue as in https://stackoverflow.com/questions/16708021/msdeploy-wmsvc-not-working ?
It appears you have to activate the web management service first and
then install web deploy and i'd done it the other way round. I
uninstalled WebDeploy and re-installed it, restarted the server and
its working
I also met the same problem. When installing WebDeploy, do not choose classic installation, but choose complete installation.
If you messed with SSL certificates this could be one of the causes as well:
https://serverfault.com/questions/613634/could-not-connect-to-remote-computer-web-deploy-error-destination-not-reachable#answer-812712