I am running a pikvm image on a raspberry pi 4 and have port forwarding enabled to be able to access it from the internet.
Since i don't have a static IP with my ISP i use no-ip service to update my hostname regularly.
Because i use this pikvm to turn on and off my home computer and that computer is not on for most of the time the No-IP DUC needs to run on the raspberry pi.
I managed to install it and run but can't run it if i try to run with the mounted disk as read-only or plan to go back to read-only state.
How can i make it able to run on a read-only mount?
I tried both running from a read-only state and read-and-write and then try to change back to read-only
Related
I have a jupyter instance running on a remote server in aws.
When I try to access it from my local computer via the browser I always get the following:
I've tried multiple different browsers and it's the same thing.
But it get's even stranger, if I fire up a terminal and just ssh into the remote aws server, nothing else, now all of a sudden I can access the jupyter instance from my local computer via the browser by just visiting the url of the notebook.
Any idea what the heck is going on here?
Here's a more detailed description. We have two machines A (local) and B (remote). On machine B jupyter-lab is installed using conda.
In order to access jupyter-lab from my local machine A I simply start jupyter-lab on machine B on port 80 and then all I have to do is to visit the url public ip/domain name of machine B in the browser of machine A.
No need for ssh tunneling cause machine B has a public ip and a domain name associated with it, e.g. machineB.aws.com:80 points to the jupyter-lab instance running on machine B.
Now the bizarre thing in all this is that visiting the url machineB.aws.com:80 from the browser in machine A always gives the error "The site can't be reached", unless I simply ssh from machine A into machine B, then the site is reachable and the url machineB.aws.com:80 works fine.
Again, no ssh tunneling going on here, simply ssh from A --> B makes the site reachable?
Clarification
This issue is being caused by the fact that I have configured jupyter-lab to run as user service via systemd. According to the wiki This process will survive as long as there is some session for that user, and will be killed as soon as the last session for the user is closed. When #Automatic start-up of systemd user instances is enabled, the instance is started on boot and will not be killed. If I'm not mistaken I have configured the user service to start-up automatically upon each boot of the computer. Which makes me a bit skeptical why process is being killed when no user is logged in?
Here's the systemd unit file configuration for jupyter:
[Unit]
Description=Jupyter Lab
[Service]
Type=simple
ExecStart=/home/user/anaconda3/envs/myenv/bin/jupyter-lab
WorkingDirectory=/home/user/
Restart=always
RestartSec=120
[Install]
WantedBy=default.target
It seems that I might have forgotten to issue the following command:
loginctl enable-linger username, which is necessary for a systemd user process to run without a user session on startup and to keep running even after a user session has been closed. This is mentioned in the wiki and also mentioned here, here and here
I have Wireguard installed on a Raspberry Pi 4 via PiVPN. The pi is plugged directly into my network switch.
I went through the setup and assigned the pi a static IP (10.0.0.157), generated a config and tried to login from my laptop (laptop was on a personal hotspot for testing purposes).
Wireguard connected using the profile and said it was sending traffic, but I was not able to load anything or ping any of the devices on my internal network.
I also noticed that my laptop was being assigned an IP of 10.0.6.1, which doesn't make sense because my network is in the IP range of 10.0.0.0/24
Any idea why this is happening or how to fix it?
I was able to fix this by changing the AllowedIPs value in the config and ensuring that I was forwarding the proper port.
I have been struggling a bit to get access to airflow from outsite my network.
I have airflow running on a raspberry pi 4, and all seems to be working just fine, I can access it via http://localhost:8080.
I have also set forwarding rules in my home router pointing to the raspberry pi:
The port forwarding is working since I can see it open using an external tool, and I have also set up a SSH port forwarding to access my raspberry pi from outside my local network.
So accessing http://my-public-ip:123 should be taking me to my aiflow web ui, but instead I just got "This site can't be reached".
Can anybody spot what I have done wrong or if I skipped any step of the process?
Thanks in advance.
Are you running Airflow with Docker or you have it installed? If using Docker, setting the webserver's service port to 127.0.0.1:8080:8080 it's the first step.
Secondly, you might need to look into the config webserver options. You will need to set the AIRFLOW__WEBSERVER__BASE_URL: 'http[s]://your_address/airflow' environment variable and install a reverse proxy (I suggest you nginx); you can find more details here. After you've done this, don't forget to also set the environment variable AIRFLOW__WEBSERVER__ENABLE_PROXY_FIX: 'true
How is a local Debian server setup so that an iphone app in the simulator can communicate with it?
I want to send files and data to the server from an iphone app. and for now I would like it to be locally using the simulator, rather than a device using a router.
Enable NAT and you will find one network on the vm and two on the host computer, being one, a virtual network shared between the two of them. Then simply use their IP addresses as they appear in ifconfig.
I'm finding that I can't access the admin shares on an XP64 box when there's no network connection. Trying to browse to \\localhost\c$ fails (although obviously browsing c: works).
Reason for the question is that the NANT build script for our application uses this format to copy files from one local directory to another, and it's failing when I'm trying to use my laptop on the train (the same problem occurs if I unplug the network cable from my desktop and build). The whole build only uses local resources so should be possible without network connection.
You could install a loopback adapter to fool the computer into thinking it's on a network. http://support.microsoft.com/kb/839013