I have installed R and Rstudio-server on Amazon AMI cloud and both are running properly as I can type R and get the R-terminal and check whether the RStudio-server is running.
sudo lsof | grep rstudio
Since Port 8787 is not accessible and there is another port something like 6970 open so I have created a rserver.conf file in /etc/rstudio/ But when I try to open RStudio server from my system's web browser I get this error
"No Data Received"
I am not sure what is the issue, any help would be greatly appreciated.
I've been using RStudio on AWS instance (EC2, Ubuntu) for several months, so I hope I can help you. First, could you clarify this part of your post?
Since Port 8787 is not accessible and there is another port something like 6970 open
I suppose you are using EC2, as it seems to be a common one for this purpose. Then, I believe you can open certain ports by configuring security groups in the AWS console (i.e. Network&Security - Security Group). Have you added a rule to allow 8787 (or 6970 if you prefer) inbound?
This worked for me.
rstudio-server online
Related
Hey this is my first question on here, so go easy.
I set up a Nextcloud server on my homelab in an ubuntu server 20.04 vm using the snap install. I have a seperate vm running nginx as a reverse proxy to my Nextcloud instance. Everything works flawlessly as intended, except that when I try and install apps on Nextcloud, I get a curl error #7. I've tried using my lan ip through the web ui, my public domain name through the web ui, and the commandline using the nextcloud.occ app:install command. I always get the same error. I tried to find the appropriate log file to get more information but looking in /var/snap/nextcloud/current/log/ I couldn't find any relevant info in any of the logs. Running php -m comes up with php not installed, I guess because php is installed via the Nextcloud snap? Obviously php is installed somewhere because Nextcloud is running, but I don't know how to look and see what modules are enabled, or how to install new ones using the snap. Any help on what to do is much appreciated!
enter image description here
Update: I fixed it. I think I had improperly configured my firewall, and turning it off (in proxmox)/making some changes to my /etc/netplan/*.yaml file to properly configure the static IP fixed it. GL
Another reason can be a wrongliy configured network. I forgot to set the gateway/proxy for IPv4, so github.com was unreachable. Most other services I use seem to resolve IPv6 first, so I did not have any other problems besides updating nextcloud apps.
Im running a small scientific cluster in our lab. Jupyterhub is installed to run jupyter notebooks with python/julia/r for multiple users. we are new to dask
Dask and the jupyterlab extensions work fine if I run them locally on a node and acces through 127.0.0.1
However I can’t get dask to play nice with the nginx proxy we normally use to connect to jupyterhub. The status pages still point to 127.0.0.1 instead of the access node IP.
Any hints are appreciated.
Our setup
Nginx<——->jupyterhub on access node
Slurm scheduler
8 compute nodes
All on same subnet
somehow, I'm not the only one. see this thread:
https://github.com/dask/dask-labextension/issues/41
however, it is totally unclear for me howto tackle this since..
If someone could outline the steps it would be really helpful.
I cannot ssh into my Google Compute Engine (GCE) Wordpress instance anymore.
It was working one month ago when I tried last.
I use the Google built-in SSH client in a Chrome browser window.
Yesterday I tried an got the following message:
The VM guest environment is outdated and only supports the deprecated
'sshKeys' metadata item. Please follow the steps here to update.
The "Steps here" link navigates to https://cloud.google.com/compute/docs/images/configuring-imported-images#install_guest_environment which does not seem to help me much.
I am not aware of any changes that I may have made.
How can I fix this?
It looks like your instance's disk is full, and so the SSH keys can't be created in the temp directory. You can do the following:
Stop your instance and wait for it to shut down
Click on the disk your instance is using, and choose "edit" at the top
Enter a larger disk size, and save
Go back to your instance and start it up again
You should now be able to connect via SSH. While you're in there, check to see what filled up your hard disk so you can prevent this from happening again (maybe a rogue program is printing out too many logs, etc).
If you're seeing this on Debian 8 or 9, the most likely reason for this is that the google-compute-engine.* packages that allow SSH access to the instance have been removed by apt-get autoremove.
If you have an open SSH connection to the machine or can use a tool like gcloud, running apt-get update && sudo apt-get install gce-compute-image-packages should fix this.
If you no longer have any SSH access, there is a procedure available on the GCP docs site that can be used to restore it.
I've created a bug report here for this.
Might be a bit late, but you can
1) Stop the VM
2) Edit and enable serial console
3) Use the serial connection to login and update the VM
recent days, I meet similar problem, later I find the permission rights of my home directory fools me, as a lazy-bone, I chmod 777 ~
After did that, I cannot ssh via my terminal, even cannot ssh via browser, only get 'The VM guest environment is outdated and only supports the deprecated 'sshKeys' metadata item, Plese follow the steps here to update'. Sounds like you must set 755 to your home dir, not just care your 700 .ssh or 600 authorized_keys.
I met the similar issue after I created a FreeBSD VM, gcloud ssh not works, but I am lucky that I can use the browser window ssh to my VM. Then I manually add the google_compute-engine public key to the .ssh/authorized_keys, now it work, I can use the gcloud ssh to connect. But not sure if this is a better/security way.
I am running RStudio server on an ec2 instance (using Louis Aslett's AMI) and connect through the browser.
I have some long scripts to run and thought I would be able to leave them running and close the browser tab/turn off my computer.
However, when I do this it seems to interrupt the console and when I log back into the server (pasting address into address bar and logging back in) I am met with an alert telling me that the R session terminated and my workspace is completely reset (working directory reset, and any data or variables lost).
Note that I am not terminating the instance, I am simply closing the browser tab that RStudio is loaded in.
Am I doing something wrong? Is there a proper way to disconnect safely and prevent this from happening?
Thanks
The author of the AMI implies that the AMI is based on Linux, so you can run screen before launching your RStudio server session.
The screen package is bundled with most Linux distributions. The author doesn't mention which distro his AMI is based on or list all of the included packages, but if the AMI doesn't have it, then you can use a package manger to install it:
sudo apt-get install screen -y
if your package manager is apt. The installation using the yum package manager is similar.
I want to install wordpress on localhost
I have downloaded and installed XAMPP.
I have downloaded the wordpress 3.4.1 and placed it in htdocs folder.and i renamed it as demo_folder.
when i type in navigation bar localhost/demo_folder it shows Unable to connect page.
As you can see the apache is not running as shown in fig.
when i click on start it doesnt get started
I dont know why?
can anyone help me out???
EDIT1
the below is netstat -an cmd screenshot
This is a fairly common problem with XAMPP/Windows. The usual suspect is that there is another application running on port 80, which you should terminate. Also please use the web, there is a wealth of information on this topic.
To view all currently open ports and the PID of the process using that port, open cmd and run
> netstat -o
This should help with changing the port Apache runs on: http://www.geckoandfly.com/7491/xampp-apache-wont-start-change-port-to-listen-85/ .
If you're on Windows 7, shut down the Web Deployment Agent Service. That should clear port 80.
XAMPP does have some problems with Windows. You could also try using WAMP. It seems to be a lot easier to install and use.
As for XAMPP, try making sure nothing else is using the port 80.
It seems you have tried to install the XAMP multiple times or PORT 80 has been used by other Application. If you are sure other applications is not using the Port 80 try this:
Close the XAMP and go to run and type services.msc and find the service named Apache 2.x.x etc go to its properties and get the exact name of it . For eg, mysql service name is mysql.
After you have found the service name , Open cmd with administrator privilege and type
sc delete apache
here is the manual to delete the service name :
http://technet.microsoft.com/en-us/library/cc742045(v=ws.10).aspx
after deleting the service name try opening the XAMP and click on Start next to Apache, hope it will be running now.
If nothing works above ,most of the cases I have seen Skype is the problem:
Go to Tools>Options>Advanced>Connections
Untick Use Port 80 for incoming connections