I have setup a Jupyter Notebook Server on an AWS server, using the Andaconda distribution. I can login to the Jupyter web application on the public IP address but Jupyter doesn't list the directories or files. I can see them when I am using the private IP address (using RDP into the machine).
I suspect it may have to do something with the windows accounts.
Any insight what I am missing?
Thanks in advance
So I found the answer myself. I have a Windows account specifically for the Jupyter user (Guest, Power User). I have tried adding Administrator to this account as well but it didn't resolve the issue.
The solution is even easier, you just have to run the Jupyter Notebook Server as Administrator.
There you have it if you ever run into the same issue that I had.
Related
I'm very new to Jupyter notebooks and recently setup a dev instance with a basic password for external access. While this works fine, I need to tie it into LDAP or PAM authentication on my RHEL server.
As I started reading about this, it appears JupyterHub is the way to go with but I'm running into some issues with that setup. I did some basic configuration and I can login fine via PAM, but it says "Spawn failed" after the login page.
Ideally I'd like to stick with just notebooks + LDAP auth if possible to make things simpler. If that is not possible, can anyone help me out with what type of configuration I need for hub to frontend notebooks and just forward to the existing setup I have?
Hub is currently running on :8000
Notebooks is currently running on :8888
I also have custom themes on Notebooks that I want to keep, even if I have to use Hub.
Any help would be greatly appreciated.
Instead of using Hub, I ended up just using Apache to front end the connection and then proxy to 127.0.0.1:8888 localhost.
This allowed me to utilize LDAP auth as well as the certificates that I'm already utilizing with Apache.
I have questions about virtual machine using vagrant. I need to install vagrant on a mac, but not for development mode. Just in production. My website runs localy on my mac and every day I need to run vagrant to use my website. It's important to know I won't to make my website online. How can I do that automatically ?
Thanks for answer.
If you need to run the vagrant up, to access your Vagrant Box, it is because your box has been turned off. Unless you are physically turning off your machine, this should not happen.
If you are using a mac you could automate the vagrant box to startup boot of your system using the automator, something like this.
https://www.lifewire.com/automate-opening-applications-and-folders-on-mac-2260908
I have successfully installed Apigility to a remote CentOS server. It tell me to go to http://localhost:8888 to access the admin panel. This server does not have a GUI installed so I don't have the ability to remote in to use a web browser. Is there a workaround to access the Apigility interface remotely, possibly restricting access to my IP address? If not do I have to install it on my local machine and then deploy my work to the remote server?
You could add a .htaccess
file
to set a password on it
If you're deploying to AWS you should be able to configure your SecurityGroup to only allow request to your installation if you're trying to access it.
if you want to develop your application right now I would recommend to have a local installation in a docker container or so to perform your changes. If you're going live you shouldn't change anything in the admin surface either.
centOS server using terminal if i am right. The best way to do this with centOs server in terminal is to open port 8888 to the public and access the server from another system serverIP:8888 (using tools like firewalld in the centOs server. U will have to install firewalld) https://www.rootusers.com/how-to-open-a-port-in-centos-7-with-firewalld/
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.
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